MR titles use issue- prefix for git-platform issues #296

Closed
opened 2026-08-21 01:46:43 +00:00 by david · 0 comments
Owner

The MR/PR title built in the mr stage was always <key>: <summary> using the raw issue key, so GitHub/GitLab/Forgejo issues produced ambiguous bare-number titles (e.g. 13: Add login page). This change introduces a shared buildIssueKeyLabel helper — single source of truth alongside branch naming — that prefixes git-platform issue numbers with issue-, so titles become issue-13: Add login page while Jira keys stay as-is (ABC-123: Add login page). Deterministic, unit-tested; no behaviour change for Jira or for branch names.

The MR/PR title built in the mr stage was always `<key>: <summary>` using the raw issue key, so GitHub/GitLab/Forgejo issues produced ambiguous bare-number titles (e.g. `13: Add login page`). This change introduces a shared `buildIssueKeyLabel` helper — single source of truth alongside branch naming — that prefixes git-platform issue numbers with `issue-`, so titles become `issue-13: Add login page` while Jira keys stay as-is (`ABC-123: Add login page`). Deterministic, unit-tested; no behaviour change for Jira or for branch names.
david closed this issue 2026-08-21 01:49:19 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
david/pi-loop#296
No description provided.