CPSC 480 SE Git Commit Messages

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