c4dbb26c1d
* feat(issue-54): backport pr commits without squash fix https://github.com/kiegroup/git-backporting/issues/54 * feat(issue-54): fixed readme
2.2 KiB
Thank you for submitting this pull request
fix (please add the issue ID if it exists)
Referenced pull requests
Checklist
- Tests added if applicable.
- Documentation updated if applicable.
Note:
dist/cli/index.jsanddist/gha/index.jsare automatically generated by git hooks and gh workflows.
First time here?
This project follows git conventional commits pattern, therefore the commits should have the following format:
<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>
Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]
NOTE: if you are still in a
work in progressbranch and you want to push your changes remotely, consider adding--no-verifyfor bothcommitandpush, e.g.,git push origin <feat-branch> --no-verify- this could become useful to push changes where there are still tests failures. Once the pull request is ready, pleaseamendthe commit and force-push it to keep following the adopted git commit standard.
How to prepare for a new release?
There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.
Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.
More details can be found in package release section of the README.