feat(core): add `ApplicationRef.destroy` method (#45624)Find a commit message that matches what you changed.
Search a curated library of commits by task, type, or scope.
Featured examples
Browse all →fix(style): remove outline transitionsdocs(router): deprecate setupTestingRouter (#48008)refactor(ext/http): remove op_http_read (#16096)perf: prevent renderer hot functions being inlined by minifiersci: Remove CodeBuild (#15887)test: add test helper for accessibilitybuild: fix npm package files inclusionchore(eslint): add tsconfig parserOptions only for ts,tsxfix(checkbox): call group.onChange only oncefix(button): undefined style props not using default stylefix(router-outlet): fix stack attribute detection (#14921)Build your commit
Assemble a commit from structured fields.
Loading builder…
What are Conventional Commits?
A Conventional Commit is a lightweight convention on top of commit messages: an explicit type, an optional scope, and a short description — optionally a body and footers.
Teams adopt the convention because it makes history scannable, powers changelog and release automation, and lets tooling derive semantic version bumps from commit types.
feat Introduces a new feature or capability.fix Fixes a bug or corrects unexpected behavior.docs Changes documentation only, such as README files or reference docs.style Changes code formatting or style without affecting behavior.refactor Restructures code without changing its behavior or fixing a bug.test Adds, updates, or fixes tests.chore Performs routine maintenance that does not affect application behavior.build Changes the build system, tooling, or external dependencies.ci Changes continuous integration configuration, workflows, or scripts.perf Improves performance without changing behavior.