-
### Description
https://www.conventionalcommits.org/en/v1.0.0/
We should write it into wiki, and link the wiki page to CONTRIBUTING.
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Feature description
When managing dependencies on major version for our code base we perform automated version…
-
Cool project!
Perhaps it would be nice to align with https://www.conventionalcommits.org/en/v1.0.0/#specification
This specification is basically an industry standard, and lots of tooling and sta…
-
Tools like [commitzen](https://commitizen-tools.github.io/commitizen/) provide a nice interface for the CLI.
It would be nice to have such a feature integrated in fork.
From https://plugins.jetb…
carun updated
3 years ago
-
We're better off with following the same structure that exists within OpenStack such as [reno](https://docs.openstack.org/reno/latest/).
-
@abrightwell @ngaumont I saw a pr comment go through earlier today talking about the changelog, and it reminded me that I've been seeing a lot of projects out there starting more and more to use "Conv…
-
Hi,
Firstly thank you very much for this handy action script 👍
Our workflows suddenly started failing this morning with the following error:
```
Error: Unable to resolve action. Repository no…
-
Read OpenWISP Commit conventions: https://github.com/openwisp/openwisp2-docs/issues/109
I still think we should keep consistency with what we've done until now, so I would use "feature" instead of …
-
```
CONTRIBUTING
.md
.rst
```
Ruby doc format?
And
```
CONTRIBUTORS(.*)
CHANGELOG(.*)
```
-
We've been looking at a few ideas and tools around shoring up our commits, making breaking changes more clear, and generally making our release, versioning, and documentation process more automatable.…