There are many excellent naming conventions regarding git branches and commits.
But what if you want something very lean and simple?
Here is a prop...
For further actions, you may consider blocking this person and/or reporting abuse
Why "feat" for commits and "feature" for branch name's?
I think it is because "feature" is what is happening in the branch and "feat" is what happened in the commit. Also the description of a commit should be written in imperative (this last part Linus Torvalds said it, the rest is just my vision of it).
Awesome! Writing good commit messages and branch naming has always been tricky for me. From now on, I'll just use this convention.
Is there any merit to differentiating branches by hotfix/, bugfix/, feature/, refactor/ etc?
We have this kind of distinction in JIRA (or any other issue tracking system), so why should we copy that into repository as well?
The release will consist of tickets that got signed off by business, so I'm thinking from repository perspective I only need to know which branch is related to signed off tickets. So maybe just dev/JIRA-XXX is plenty?
I've been differentiating branches as mentioned by the OP as this allows me to quickly tell what the branch is about, rather than having to open up JIRA to find the title/description associated with the ticket ID.
The downside is the branch names can get pretty lengthy but I don't mind.
Thanks
Great article. Thanks.
why not add the issue/ticket number in the commit messages as well? So that even after the branch is merged each commits can be traced to that issue/task.
I've heard its bad practice to use the default merge commit message (though I haven't looked into why), but if you do it will be there. Assuming you're creating merge commits that is.
I don't really like the idea of repeating information in every commit unless I can automate it (reliably).
That's a great explanation! Thanks!
okay that's pretty helpful, thanks 👍
This is a good post. Thanks.
Amazing article, I get a clear understanding of how to write the commit message or create the branch and its naming convention.
honestly best advice ever, thanks!
Great article!! Thanks