Closing tabs and I came back across conventionalbranch.org. I know this isn't your argument, just passing on info.
But holy heck, I really have to argue with their literal first point. All lowercase, for what reason? It's never explained why they insist on a dated convention instead of proper style.
And in what world is "feat/" abbreviation considered allowable?
I lump this in with advice from people who put their source in a src/ folder instead of Source/.
Comments
I think this comes from Conventional Branching, https://conventionalbranch.org, inspired by conventional commits (e.g. https://www.conventionalcommits.org/en/v1.0.0/)
Closing tabs and I came back across conventionalbranch.org. I know this isn't your argument, just passing on info.
But holy heck, I really have to argue with their literal first point. All lowercase, for what reason? It's never explained why they insist on a dated convention instead of proper style.
And in what world is "feat/" abbreviation considered allowable?
I lump this in with advice from people who put their source in a src/ folder instead of Source/.
And my point is that this pattern is now more popular than it was 3 years ago. Similar to people using the phrase "load bearing".
For me, this popularity is graphable. Telling me it's a convention doesn't change that fact. I'm sorry.