4 ms·
Past commit messages have 2 uses to me. - Blame view, where I usually want to know the ticket number so I can track down a story which has the business rules t
by graypegg 3y ago
Past commit messages have 2 uses to me.
- Blame view, where I usually want to know the ticket number so I can track down a story which has the business rules the dev was implementing.
- Bisect, where I want to know if this works or not without having to do a test run every time.
This format is alright I guess, but the best thing you can do honestly is just
TICKET: [done/works but wip/does not work] [describe what you’re thinking]
AB-1234: does not work, trying to rewrite this controller to remove all the duplication, /api removed temporarily
To me, that doesn’t have to be set in stone. No one likes working with a commit message stickler when standardized formats are only useful ~20 times a year to save 10 minutes each. (In my experience)