chore(git-hooks): migrate branch naming from jira to linear convention [ENG-538] - #2
Open
quentinLhotellier wants to merge 1 commit into
Open
chore(git-hooks): migrate branch naming from jira to linear convention [ENG-538]#2quentinLhotellier wants to merge 1 commit into
quentinLhotellier wants to merge 1 commit into
Conversation
…n [ENG-538] Replace the Jira-style branch policy (<type>/<subject>/<jira_ref>) with the Linear convention (eng-<n>-<scope>-<short-desc>, regex ^eng-[0-9]+-[a-z0-9]+(-[a-z0-9]+)*$). Keep escape hatches for non-feature branches (HEAD, main/master/develop, preprod/staging, release/*, experimental/*) and consolidate all invalid cases into a single clear error message. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
quentinLhotellier
requested review from
TheCrab13,
jb-machemie,
loicknuchel,
mathieubotter and
mcoutantL
July 27, 2026 20:44
Contributor
|
aujourd'hui il n'est pas possible de faire une telle modification dans ce repo car il est utilisé par d'autres personnes. Effectivement, ce dossier étant public, une telle modification casserait les installations de tous les gens qui les utilisent |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Replace the legacy Jira-style branch-naming policy in the
pre-commithookwith the new Linear convention.
<type>/<subject>/<jira_ref>(e.g.feat/foo/EXT-123)<linear-ticket>-<scope>-<short-description>^eng-[0-9]+-[a-z0-9]+(-[a-z0-9]+)*$eng-145-extranet-front-document-previewDetails
check_branch_name()around the Linear regex.HEAD,main/master/develop,preprod/staging,release/*(now permissive — allows e.g.release/extranet-legacy),experimental/*.report_invalid_format).(
report_invalid_type,report_invalid_jira_ref,TYPELIST,commit_types.confblock).commit-msghook unchanged (already acceptstype(scope): subject [ENG-nnn]).Net:
-91 / +25.bash -nclean; tested against valid/invalid branch names.Rollout
After merge, each consuming repo picks it up with
make install/make git-hooks(re-runs
doInstall.sh).Ref: ENG-538
🤖 Generated with Claude Code