Closed Lucianovici closed 3 years ago
@Lucianovici could you update both commit messages to comply with conventional commit standard. see https://www.conventionalcommits.org/en/v1.0.0/#summary CI is failing.
@noelmcloughlin Is it important to fix this?
The solution of renaming pushed commit messages is not ideal (forcing to push) - is there another way I am not aware of?
Is it important to fix this?
Yes. All automation based on conventional commits (widely used today instead of unconventional commits) breaks. Someone would have to change those commit messages to get CI and Semantic Release working.
@noelmcloughlin Since I am a casual committer, can we do as advice here please? https://www.conventionalcommits.org/en/v1.0.0/#do-all-my-contributors-need-to-use-the-conventional-commits-specification
I'm not maintainer, just passing by, so its extra workload. I think its possible, I've never done that, I could try I guess. https://github.com/saltstack-formulas/node-formula/blob/79081c913440a83104ed3b7347c777e2eb9f4773/CODEOWNERS#L11-L12
Okay, that did not work, I'll try to remember to open a new PR to fix your commit messages. Please use conventional commits in future, its considered impolite to use unconventional commits these days.
Alright thank you, I will use the convention from now on. But why didn't it work, I just alter the history and force push it.
Just noting that this is an example of a patch for this Salt regression as mentioned here:
We may want to revert the with context
changes if that upstream regression is fixed in an appropriate way.
:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Import with context to avoid errors like: