Adopt Conventional Commits as standard to all commits #3
Labels
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/go-abra#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 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)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.
Saw that we can run a CI check that'll lint the commit messages for format:
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