1/23/2024 0 Comments Git hub pull request![]() footers other than BREAKING CHANGE: may be provided and follow a convention similar toĪdditional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE).Ī scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.types other than fix: and feat: are allowed, for example (based on the Angular convention) recommends build:, chore:,Ĭi:, docs:, style:, refactor:, perf:, test:, and others.BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning).Ī BREAKING CHANGE can be part of commits of any type.feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).The commit contains the following structural elements, to communicate intent to the ![]() The commit message should be structured as follows: Which makes it easier to write automated tools on top of.īy describing the features, fixes, and breaking changes made in commit messages. It provides an easy set of rules for creating an explicit commit history The Conventional Commits specification is a lightweight convention on top of commit messages. Quick Summary Full Specification Contribute Conventional Commits 1.0.0 Summary
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |