Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
People write comments like this one because it's useful to know the published release in which the issue is fixed.
Not sure how many developers missing this information, but I certainly do.
Is that something that can be done in automatic way? Or it can only be a property on issue?
Comment | File | Size | Author |
---|
Comments
Comment #2
drummIssues are already complicated enough, I'd want this to be automatic only. The tricky part is having a good algorithm for it. For example, some issues have bits of fixes that arrive in multiple versions.
Might want to move this to versioncontrol_project's issue queue if we depend on commit messages.
Comment #3
Leksat CreditAttribution: Leksat at Amazee Labs commentedWhat about the following?
If we add output of "git tag --contains={hash}" to commit messages?
Maybe not all tags, but just the first one. Or first ones from each branch. Anything would be helpful.