{
  "$type": "site.standard.document",
  "canonicalUrl": "https://www.simoncox.com/short-articles/2024-12-14-git-commit-messages/",
  "description": "Stealing Angie's Commit messages for my 11ty needs ensuring that I have a more robust method of tagging my commits so that they can be easily differentiated.",
  "path": "/short-articles/2024-12-14-git-commit-messages/",
  "publishedAt": "2024-12-14T11:49:00.798Z",
  "site": "at://did:plc:tki7vwlanxbwrz2er67eaeqa/site.standard.publication/3mp4h4md7zv2y",
  "tags": "Eleventy",
  "textContent": "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\".\n\nWhat a great idea!\n\nI 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.\n\nSo here is my extended version:\n\n feat: anything feature related, even if deleting code or making changes to existing features\n fix: fixing a bug or issue without new feature code\n refactor: code change that neither fixes a bug nor adds a feature but somehow improves the codebase (for me this is usually streamlining CSS)\n cms: changes to the CMS (version updates or plugin updates, installs, or removals)\n build: Changes that affect the build system or external dependencies, such as npm, DDEV setup, or Laravel Mix.\n content: New content, images and typo fixes and corrections\n* seo: Changes optimising code or content for seo purposes\n\nThat should see me right!",
  "title": "11ty Git Commit Messages"
}