Skip to content

Commit

Permalink
git: explicitly say that it's OK to fix #28
Browse files Browse the repository at this point in the history
Commit messages can be short in which case it's OK to put references into
the header, adding some longer body just to put the references doesn't improve
things much.

Signed-off-by: Roman Khimov <roman@nspcc.ru>
  • Loading branch information
roman-khimov committed Sep 10, 2024
1 parent 36dae73 commit bddc739
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions git.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,7 @@ repository, in this case the subsystem prefix MAY be omitted.

If commit fixes some issue it MUST be mentioned in the message using "fixes
XXX" (or "closes XXX") notation to automatically close the respective issue.
These references MAY be placed in the short description (header) if they fit.

Description MUST contain enough data to understand what's going on without
looking at the linked issues (they're additional data, not the primary thing
Expand Down

0 comments on commit bddc739

Please sign in to comment.