README: Add a link to the commitlink project#152
README: Add a link to the commitlink project#152wagoid merged 1 commit intowagoid:masterfrom sschuberth:patch-1
Conversation
jdbruijn
left a comment
jdbruijn
left a comment
There was a problem hiding this comment.
I'd argue it should link to https://commitlint.js.org/#/, which is their main page as far as I know.
wagoid
left a comment
wagoid
left a comment
There was a problem hiding this comment.
Thanks for the contribution! One small detail, your commit message needs to have a valid subject. So instead of README: you can use docs: or docs(README):
You can see more details about the lint failure here: https://github.com/wagoid/commitlint-github-action/pull/152/checks?check_run_id=2499490935
|
Sorry @sschuberth one more rule that I forgot in my suggestion: https://github.com/wagoid/commitlint-github-action/pull/152/checks?check_run_id=2499607746 |
Done. |
|
Last one! |
Already did that in parallel. Actually, this was a nice showcase, and probably showed me that these conventions are not for us 😉 |
|
@sschuberth you can configure them, and remove whatever conventions you think is not fit for you. For example, in the company I work we allow any scope case so that we can put jira tickets in the scope. You can set your commitlint config file to make things as loose as you want 🚀 |
3 participants
No description provided.