Skip to content

Feature Request: Configurable branch naming besides prefix #566

@BOLT04

Description

@BOLT04

Add support for configurable branch naming conventions to follow other branching strategies (e.g. GitFlow), allowing teams to customize branch prefixes based on issue types. Ideally we could define Git Instructions in CLAUDE.md and claude would suggest the branch name following those suggestions, instead of just configuring branch prefix. The github action code would then use that.

Currently we can edit the branch prefix and the type can only have "pr" or "issue":

const branchName = `${branchPrefix}${entityType}-${entityNumber}-${timestamp}`;

Could we have this branch name done by Claude, with a fallback being the current logic?

Examples
Text in CLAUDE.md:

## Git instructions
- Please name any branch you create with our **naming conventions**:

| Branch type | Examples |
| --- | --- |
| Bugfix | bugfix/issue-123-small-description |
| Feature | feature/issue-456-small-description |
| None or Task | task/issue-999-small-description |

Output branch name for Claude:
Issue with "bug" type or label: bugfix/issue-123-small-description
Issue with "feature" type or label: feature/issue-456-small-description
Issue with no matching labels or no defined type: task/issue-999-small-description

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfeature-requestp2Non-showstopper bug or popular feature request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions