Support private and proposed update branches
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
I love the usage of git feature|bug|refactor. But it would be nice to have the same for private branches like
<username>/<branchname>
and proposed update branches
pu/<branchname>
Because those branches are good markers (when they are online/pushed to remote) that these branches are maybe rebased and should not touched by another developer.
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 at the entry points implementing git feature, git bug, and git refactor, then trace how branch names are classified. Add equivalent handling for / and pu/, while preserving the existing conventions. Done means both branch forms are recognized consistently and existing behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100