TPXimpact DX Tech Handbook
  • DX Tech Handbook
  • Processes
    • Decision making
      • RFC Template
    • Communities of practice
    • Dealing with change
    • AI generated code
    • Guidance on billing for junior developers
    • Our hiring process
    • Job Descriptions
  • Working practices
    • Version control
    • Drupal 9 upgrade
    • Site health check list
  • Best practice
    • Non functional requirements
    • Security updates
    • Browser compatibility and testing
    • Writing good commit messages
    • 🚛Load testing
  • 📕Recommended reading
  • Learning resources
    • Learning Drupal
    • Contentful training
    • Acquia DAM Certification
Powered by GitBook
On this page

Was this helpful?

  1. Best practice

Writing good commit messages

PreviousBrowser compatibility and testingNextLoad testing

Last updated 2 years ago

Was this helpful?

This process was written a long time ago and is due for review. It's been left here in case it's useful to you, but a different approach may apply for your projects.

This is a guide to writing better commit messages in order to help maintain the git logs, and provide better information for future debugging and development. Follow the link below to see the slidedeck outlining this process.

This work is licensed under a .

Creative Commons Attribution-ShareAlike 4.0 International License
Creative Commons Licence
https://docs.google.com/presentation/d/1XGwKiUaOOnpRQVZ9VfBNFQ3tZR6GT4jKP6l25EH1ZHQ/edit#slide=id.gc6f9e470d_0_0docs.google.com