You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One often names branches after issue numbers or something else, which is a good practice for long-term reference, but doesn't help one pick apart which branch is about what at-a-glance.
Proposal:
Make start take an extra optional description arg: git wf start <branch-name> [description]
Store it in .git/config by calling: git config branch.<branch-name>.description <description>
Display it at various times when it would currently only print the branch name.
Offer something like git wf branch that is an enhanced version of git branch - maybe only lists wf-managed feature branches and includes their descriptions?
Note that this is the "standard" place to store a branch description in git; it's the one that git branch --edit-description operates on. Currently it's not used for a lot inside of git itself, but maybe that will change?
The text was updated successfully, but these errors were encountered:
One often names branches after issue numbers or something else, which is a good practice for long-term reference, but doesn't help one pick apart which branch is about what at-a-glance.
Proposal:
start
take an extra optional description arg:git wf start <branch-name> [description]
.git/config
by calling:git config branch.<branch-name>.description <description>
git wf branch
that is an enhanced version ofgit branch
- maybe only lists wf-managed feature branches and includes their descriptions?Note that this is the "standard" place to store a branch description in git; it's the one that
git branch --edit-description
operates on. Currently it's not used for a lot inside of git itself, but maybe that will change?The text was updated successfully, but these errors were encountered: