conventional-changelog/conventional-changelog: Generate changelogs and release notes from a project's commit messages and metadata. ·
github.com · 497 words · saved by 1 readers
Generate changelogs and release notes from a project's commit messages and metadata.
Generate a CHANGELOG from git metadata. Getting started The original conventional-changelog package repo can be found in packages/conventional-changelog. If you are new to Conventional Commits, we recommend to read The Complete Guide. We recommend considering the following high level tools for automating versioning, tagging, and CHANGELOG generation: commit-and-tag-version — a drop-in replacement for npm's version command, handles automated version bumping, tagging, and CHANGELOG generation. semantic-release — fully automates the release process from CI/CD, including version…
saved by
related reading
- Conventional Commitsconventionalcommits.org
- Keep a Changelogkeepachangelog.com
- Semantic Versioning 2.0.0 | Semantic Versioningsemver.org
- How to Write a Git Commit Messagecbea.ms
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- Best practices for Claude Code - Claude Code Docsanthropic.com
- A successful Git branching model >> nvie.comnvie.com
- GitHub · Change is constant. GitHub keeps you ahead.github.com
- GitHub - EveryInc/compound-engineering-plugin: Official Compound Engineering plugin for Claude Code, Codex, Cursor, and moregithub.com
- GitHub - ccusage/ccusage: npx ccusagegithub.com
- GitHub - affaan-m/ECC: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.github.com
- Useful git commands for SRE and DevOps engineersreliabilityengineering.substack.com