- 🇳🇱Netherlands bbrala Netherlands
Is this a dupe, or more correctly, a predecessor? :)
🌱 [policy] Decide on format of commit message Active
📌 Change format for git commit message Active
We want to be able to automate as much as possible for release management.
Set up semantic-release to automatically bump versions and create changelogs. Using this tools means making use of a more conventional commit format such as: https://www.conventionalcommits.org/en/v1.0.0/ and enforcing this standard with a tool such as commitizen
The only addition to this would be to define a "Credit" or "By" footer listing all users to be credited for a particular issue/commit..
An example of a commit (taken from once history):
fix(once): Error when context.querySelector() doesn't find an element on the page
Credits: nod_, Danny Englander, droplet
Refs #3204168
Here the (once) is optional, in the mono repo we might want to explicitly tell which package we're handling (semantic release tools don't need it to know which package is impacted by the commit, so totally optional, only for humans).
Active
Other
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this a dupe, or more correctly, a predecessor? :)
🌱
[policy] Decide on format of commit message
Active
📌
Change format for git commit message
Active