I know this strategy and it is better than, 'Updated README'.
Unfortunately ticket references might be short lived (new ticket system) or not always accessible (only available online and with vpn). So I would not rely too heavily on this.
Short non technical description sounds good though.
I know this strategy and it is better than, 'Updated README'.
Unfortunately ticket references might be short lived (new ticket system) or not always accessible (only available online and with vpn). So I would not rely too heavily on this.
Short non technical description sounds good though.
If a new ticket system comes in, a new feature branch (from the previous feature branch) is easy.
If the ticket system isn't available, remote changes probably aren't either, so a PR / MR isn't possible.
Yeah, but the code and the repo is there. I can work, but not understand the commit 😉
It's a bit of an edge case, but living in Germany and traveling by train teaches you not to rely on your internet connection 😅
Isn't that the edge case that gave rise to the ability to edit commit messages after the fact? ;)