New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer mention issue and PR numbers in commit title #79
Comments
70? 2 8 0 ! Your proposal looks good to me. |
I agree, but let's also use prefixes for the issue and PR numbers -- for example:
Where "Issue" can be:
|
@sbrannen Are the replacements for "Issue" meant to be GitHub keywords? If so, we have to get rid of the colon, don't we? |
I just looked over the list of commits and I have to say, I really like what I see: the issue and PR numbers out in the open. Are we sure we want to give that up? Since I seem to be the only one thinking "No" and ... team ... democracy ... yadda yadda yadda 😉 ... check #86. |
Jein ("yes & no" for non-German speakers). 😉 It's a mix. See explanation here: #86 (comment)
Nope. GitHub has no problem with the colon. |
The contribution guidelines defined the following outline for commit messages, where the first line (let's call it "title") has an ideal length of 50 characters, with a maximum of 70: ${action} (${issues} / ${pull-request}) ${body} Mentioning issue and pull request numbers in the title has the advantage of making them very visible, for example in `git log --oneline` and GitHub's UI, but has the downside of severely reducing the number of available characters for the title itself. Once we cross into three digit issue/PR numbers `(#abc / #xyz)` eats up at least 14 characters - that's not good. The new guideline places issue and pull request number at the bottom of the message: ``` ${action} ${body} ${references}: ${issues} PR: ${pull-request} ``` Here, `${references}` is usually _Closes_, _Fixes_, or _Resolves_, but if none of that is the case, can also be _Issue(s)_. Closes: #79 PR: #86
The current contribution guidelines define the following outline for commit messages, where the first line (let's call it "title") has an ideal length of 50 characters, with a maximum of 70:
Mentioning issue and pull request numbers in the title has the advantage of making them very visible, for example in
git log --oneline
and GitHub's UI, but has the downside of severely reducing the number of available characters for the title itself. Once we cross into three digit issue/PR numbers(#abc / #xyz)
eats up at least 14 characters - that's not good.As an alternative, issues and pull requests could be added as a last line to the message:
Opinions?
The text was updated successfully, but these errors were encountered: