|
|
|
|
|
|
by steve_adams_86
2399 days ago
|
|
|
I've been using the same branching strategy for about 5 years, and it has worked really well. I suspect it's fairly common, although everywhere I've worked we've switched to this from something with less structure. Essentially the branch naming pattern looks like: [ticket-type]/#TICKET-[ticket-description]
In practice it might look like: bug/APP-123-prevent-auth-redirect-loop
It makes it so you can easily automate ticket statuses with commits and merges, grep for types of issues without needing to type/remember an emoji, and you don't need to worry about emojis rendering differently on different platforms. The text will always be the same.The emoji thing is fine if it's for fun - we should all enjoy ourselves and our work a little more - but I'm hard pressed to see the practicality of it. |
|
|
The first thing that comes to mind is that it takes up less space and is thus easier to scan. Also, people with visual impairments may have an easier time scanning based on color/shape rather than reading each individual line.
Also, it's just as easy to grep for ':bug:' than 'bug', or rather, it's more specific to do so. Likewise, people suggesting [bug] have to worry about whether their shell or grep is going to interpret the square brackets (they will).
git log | grep '[bug]' - does not do what you want
git log | grep [bug] - fails in ZSH; works as above in bash
git log | grep bug - matches lots of things, not just the tag
git log | grep ^bug - Doesn't work because 'git log' puts spaces in front of commit lines
git log | grep :bug: - Does exactly what you expect it to and nothing else.
That's the practicality that I see, personally.
> you don't need to worry about emojis rendering differently on different platforms
You don't really need to worry about that anyway, as long as you're generally on the same one or two platforms. A user on Ubuntu will always see the same bug, even if :bug: gives them a different bug illustration than an iOS user sees. In the git commits, it's represented as the tag (:bug:) and not the literal emoji.
Lastly, I fail to see anything that has to do with branching strategy with regards to emoji. This is purely commit messages and (in this case) the readme. Your branching strategy doesn't tell us anything about individual commits.