Conventional Commits

The Conventional Commits format — also called "semantic commits" / semantic commit messages — a `type(scope): description` header (`feat`, `fix`, …) plus an optional `BREAKING CHANGE` footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR title, deciding the type/scope/bump for a change, setting up or fixing a repo's commit convention, making commits parseable by semantic-release / changelog tooling, validating PR titles, or when a release didn't bump or the changelog came out blank because a commit wasn't conventional. Covers the type→semver mapping, breaking changes, scopes, monorepo scopes, and squash-merge PR titles.

wiiiimm Updated
glassOS — a desktop made of glass-gl surfaces: menu bar, dock, and draggable app windows (including the Spotify Music and YouTube Video apps) refracting a flora

File contents

wiiiimm/glass-gl commit 499562fdd5

Frequently asked questions

npx get-skill add wiiiimm/conventional-commits