[Bug]: Follow change request templates ignores GitLab and Azure DevOps templates
Author: BradyHazellCreated Sep 17, 2026Updated Sep 18, 2026
Labelsbuggood first issueacceptedvia-triage
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
- Use a project hosted on GitLab or Azure DevOps.
- Commit a template to the repository’s default branch:
- GitLab: .gitlab/merge_request_templates/Default.md
- Azure DevOps: .azuredevops/pull_request_template.md
- Give the template distinctive headings, such as ## Context and ## Verification.
- Enable Settings → Source Control → Follow change request templates.
- 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.
Source: pingdotgg/t3code