pingdotgg / pingdotgg/t3code

[Bug]: Follow change request templates ignores GitLab and Azure DevOps templates

Open
#12,330 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug good first issue via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Use a project hosted on GitLab or Azure DevOps.
  2. Commit a template to the repository’s default branch:
    • GitLab: .gitlab/merge_request_templates/Default.md
    • Azure DevOps: .azuredevops/pull_request_template.md
  3. Give the template distinctive headings, such as ## Context and ## Verification.
  4. Enable Settings → Source Control → Follow change request templates.
  5. Create a pull request or merge request through T3 Code’s Git actions.
Expected behavior

When enabled, the setting discovers the hosting provider’s repository template and uses it to generate the description.

Actual behavior

Template discovery is explicitly restricted to GitHub. GitLab and Azure DevOps templates are not passed to the description generator, regardless of the setting.

GitManager.ts:2023 checks provider.kind === "github" before calling detectPrTemplate. The detector in PrTemplateDetection.ts only includes GitHub-compatible paths.

Impact

Minor bug or occasional failure

Version or commit

main @ e26af33b22

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

Manually apply the template when editing the generated request description.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in GitManager.ts around line 2023 and trace the detectPrTemplate call into PrTemplateDetection.ts. Compare the existing GitHub-compatible paths with the GitLab and Azure DevOps paths named in the issue. Done means enabled Follow change request templates discovers those provider templates and uses them when creating the request description.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.