CPSC 480 Git Commit Messages

Edit Answers
12345678910111213141516
Across
  1. 4. Subject line should _______ changes briefly, ideally under 50 characters
  2. 5. Include the ______ number if the commit fixes a known issue in tracking systems
  3. 8. Limit for the length of the Git commit message's subject line is ____ characters
  4. 11. The number of characters per line recommended for wrapping the commit message body is ____ two
  5. 13. Apply a ______ style across commits to maintain readability in the history
  6. 14. The first line of a commit message should be a short ______, describing the change
  7. 15. Use the ______ tense for the commit message, describing what the change does
  8. 16. A tense to avoid when writing the commit message subject line is the ____ tense
Down
  1. 1. Separate the subject line from the body with a _____ line
  2. 2. Write commit messages in the ______ grammatical mood, like "Fix bug"
  3. 3. Avoid using ______ at the end of the subject line
  4. 6. The first letter of the commit subject should be ________
  5. 7. Avoid using ______ person perspective; describe changes without "I" or "We"
  6. 9. Commit messages should describe ______ types of changes, complete in one go
  7. 10. The commit message should provide ______ about the changes made
  8. 12. Commit messages should primarily focus on explaining ______, rather than what or how