Allow customization of issue generated branch names
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Currently gitpod only allows for creating a workspace and branch from an issue with this naming scheme:
<your-username>/<issue-title>-<issue-number>
But since many teams use different branch naming schemes, it would be very nice to be able to customize this. Ideally something we could just set in the .gitpod.yml with optional pre-defined variables (issue-title, username, issue-number, etc.) available that could be interpolated in a format that gitpod could parse.
For example:
branch_naming:
issue: "task-<issue-number>/<issue-title>"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the issue-driven workspace and branch creation flow and the .gitpod.yml configuration handling. Define how branch_naming.issue and variables such as issue-title, username, and issue-number should be parsed, then verify that the configured pattern produces the requested branch name while preserving the existing default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100