-
-
Requiring commit subjects **not** to be capitalized is a common practice especially with conventional commit implementations. There does not seem to be a way to enforce this with committed, and it wou…
-
Just had my first breaking change, and it's made me realize we need a way to separate breaking and non-breaking changes.
I think a good way of getting started here is to implement Conventional Commit…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Package ecosystem
All
### Package manager version
*
### Language version
*
### Manifest location and cont…
-
As we are using semantic versioning it is critical to understand the nature of the changes when creating releases. For example, if the release branch has some commits on it which have not been release…
-
The Conventional Commit specificiation would benefit from an explicit definition of what its own version numbers mean.
For example, let's say I convince you to add `feature` as a synomym of `feat`.…
-
Hi there? Is it possible to support conventional commits and [emojis](https://github.com/ellerbrock/conventional-commit-types-emoji) by leveraging a configuration file. Or another convention like this…
-
Parse commit summary (introduced in #5) from literal commits like:
```
docs: add section on testing in contributing guidelines
fix(cli): enable --no-colors flag to mute the output
chore(deps): …
-
I propose to add the usage of conventional commits acc. to https://www.conventionalcommits.org/en/v1.0.0/ to our contribution guideline.
No hard enforcement, but would be nice to have them i.e. to ge…
-
Learn Conventional Commits v1.0.0 syntax and begin applying that style to this repository. It will be CORE to the functionality of this project. All commits will be parsed off this syntax to generate …