![]() Types other than feat and fix MAY be used in your commit messages.The footer MUST only contain BREAKING CHANGE, external links, issue references, and other meta-information.Has changed about the API, e.g., BREAKING CHANGE: environment variables now take precedence over config files. A description MUST be provided after the BREAKING CHANGE:, describing what.A breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon and a space. Breaking changes MUST be indicated at the very beginning of the footer or body section of a commit.The footer SHOULD contain additional issue references about the code changes (such as the issues it fixes, e.g., Fixes #13). A footer MAY be provided one blank line after the body (or after the description if body is missing). ![]() The body MUST begin one blank line after the description.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |