4 ms·
Yeah, but none of that would be affected right? If you don't prepend the ticket number, it'll do it for you. That gives the entire team a guarantee all the work
by james_s_tayler 8y ago
Yeah, but none of that would be affected right? If you don't prepend the ticket number, it'll do it for you. That gives the entire team a guarantee all the work is traceable. It's a tool that serves the whole team, not just you.
- ninkendo 8y agoWhy should this be done at pre-commit time? And what automated system will be able to guess a ticket number based only on what's in a commit? I'm all for validation that all commits must have some metadata/ticket numbers attached... at the time it is merged into master. Not on my local machine. I probably did `git add -A && git commit -m WIP` at least 7 or 8 times today alone. But all my commits that made it into a PR were squashed, divided up logically, and renamed before they went in. I'm trying to imagine a system where some automated thing prepends "TICKET#123 WIP" before every commit I make, locally, even if they're all getting thrown away before I squash/rebase/reword my commits. What's the point?