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

Jump to bottom

add branch naming conventions rule #173

Open

bgeck wants to merge 1 commit into elsewhencode:master from bgeck:feat/branch-naming-conventions

bgeck commented Mar 5, 2024 •

edited

Loading

Add a branch naming convention rule to encourage organization and consistency in feature branch names.

I've found this very useful working in teams, both to help teammates stay organized when thinking about how many chunks to break a TODO into like:

[type]/[task-id]/descriptive-text

feat/1234/datatable-ui-layer
feat/1234/datatable-api-logic
etc....

and also to help communicate to each other and to PMs what a branch is for, even weeks later ;)


          add branch naming conventions rule

1ef3066

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet