11ty Git Commit Messages

SimonCox December 14, 2024
Source

Just read Git Commit Messages by Angie Herrera who has started organising Git Commit Messages "in a way that keeps things organized and makes future me a bit happier and less stressed".

What a great idea!

I decided I am going to do the same – so I copied Angie's bullet points into a Note and then started thinking about it. Angie is a very accomplished Craft CMS developer, who I have been honoured to provide some SEO work, so the list makes perfect sense for a Craft build. However with 11ty builds I needed something a little more because I am now also making content changes in my 11ty builds.

So here is my extended version:

feat: anything feature related, even if deleting code or making changes to existing features fix: fixing a bug or issue without new feature code refactor: code change that neither fixes a bug nor adds a feature but somehow improves the codebase (for me this is usually streamlining CSS) cms: changes to the CMS (version updates or plugin updates, installs, or removals) build: Changes that affect the build system or external dependencies, such as npm, DDEV setup, or Laravel Mix. content: New content, images and typo fixes and corrections

  • seo: Changes optimising code or content for seo purposes

That should see me right!

Discussion in the ATmosphere

Loading comments...