Adopt Conventional Commits as standard to all commits #3

New Issue

2021-07-16T07:39:09Z

roxxers commented

2021-07-16 07:39:09 +00:00

I plan to use Sematic vesioning and we can use conventional commits to both automate this vesioning but also allow for commit messages that better explains the changes. I have been using them in all of my commits in this repo.

https://www.conventionalcommits.org/en/v1.0.0/

I plan to use Sematic vesioning and we can use conventional commits to both automate this vesioning but also allow for commit messages that better explains the changes. I have been using them in all of my commits in this repo. https://www.conventionalcommits.org/en/v1.0.0/

roxxers commented

2021-07-16 08:35:55 +00:00

I go into detail about the reasoning behind commits, inspired by this blogpost https://dhwthompson.com/2019/my-favourite-git-commit.

My recent commit is an example of what I strive to do. 5e1b076bf9 This one isn't always possible but I would like people to think about using more detail in commits (without going over the first line char limit which is like 70~ chars)

I go into detail about the reasoning behind commits, inspired by this blogpost https://dhwthompson.com/2019/my-favourite-git-commit. My recent commit is an example of what I strive to do. 5e1b076bf9 This one isn't always possible but I would like people to think about using more detail in commits (without going over the first line char limit which is like 70~ chars)

decentral1se commented

2021-07-16 10:50:57 +00:00

Looks good, I will use the conventional commits style from now on and keep in mind that my commits could be used for a change log. We can document this in the README if other folks don't have issues with it.

decentral1se commented

2021-07-17 21:31:38 +00:00

Saw that we can run a CI check that'll lint the commit messages for format:

https://github.com/conventional-changelog/commitlint

Saw that we can run a CI check that'll lint the commit messages for format: > https://github.com/conventional-changelog/commitlint

roxxers commented

2021-07-21 06:59:03 +00:00

Saw that we can run a CI check that'll lint the commit messages for format:

https://github.com/conventional-changelog/commitlint

Looks good but I worry about the effects of doing that post commit and push where the history is now in a repo where it would be bad to force it to be correct

> Saw that we can run a CI check that'll lint the commit messages for format: > > > https://github.com/conventional-changelog/commitlint Looks good but I worry about the effects of doing that post commit and push where the history is now in a repo where it would be bad to force it to be correct

decentral1se referenced this issue from a commit

2021-08-10 18:14:04 +00:00

docs: add notice about conventional commits

decentral1se closed this issue

2021-08-10 18:14:04 +00:00

3wordchant referenced this issue

2025-08-11 10:14:56 +00:00

autocomplete on `abra recipe upgrade` is slow #567

Sign in to join this conversation.