3 ms·
Yeah, I pretty strongly agree that it shouldn't be in commit messages. A big consideration for us was that we didn't want to get in the way of normal developme
by ddulaney 2y ago
Yeah, I pretty strongly agree that it shouldn't be in commit messages.
A big consideration for us was that we didn't want to get in the way of normal development, and Git is a core part of that loop. By making the release note a thing that happens separately, we let devs batch that work before a release. But the tool displays the commit right as you're writing the note, so you can quickly see what internal-facing commit message you wrote at the time, and copy-paste if you think it's good enough.
- keybored 2y agoI love that approach. Everything is linked but nothing pollutes the wrong context.