Skip to content

Update naming convention for component feature branches #960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
eidenyoshida wants to merge 2 commits into from
Closed

Update naming convention for component feature branches #960

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
436d54b
Update naming convention for component feature branches
eidenyoshida Jul 30, 2025
01909ce
Merge branch 'develop' into users/eyoshida/branch-naming
eidenyoshida Sep 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,8 @@ During this period, a high priority will be placed on keeping the `develop` bran

When creating a branch for your work, use the following convention to make branch names informative and consistent: `users/<github-username>/<branch-name>`.

For component specific feature branches, use the following convention: `<component>/<feature-branch-name>`.

Try to keep branch names descriptive yet concise to reflect the purpose of the branch. For example, referencing the GitHub Issue number if the pull request is related.

The build and test infrastructure has some tasks where pull requests from forks have fewer privileges than pull requests from branches within this repo. Thus, branches in this repo are encouraged but you are welcome to use forks and their potential gaps. We are actively working towards achieving feature parity between pull requests from branches and pull requests from forks. Please stay tuned.
Expand Down