Use git-commit-template
for
commit messages guidelines. More information
Read about Conventional Commits.
- Provide proper comments
- Try not to keep more than 72 chars per line
- Commit any sensitive information
- Commit trailing whitespaces
- Keep an empty line at the end of any file
- Rebase your
fix
branch on top of thetarget
branch before creating a PR - Update README.md to reflect breaking changes
- Do not use GitHub's
Merge Changes
button to merge PRs. It creates unnecessary merge commits - Fetch the
fix
branch locally using GitHub'spull
refspec - Rebase the
fix
branch on thetarget
branch - Merge
fix
branch intarget
branch
Source: https://git-scm.com/book/en/v2/GitHub-Maintaining-a-Project#_pr_refs
Strictly follow Semantic Versioning.
Use semantic-release:
Action | Snippet |
---|---|
Install | npm install -g semantic-release@15 |
Access Token | export GITHUB_TOKEN=XXXXXXXXXXXXXX |
Dry run | semantic-release -d |
Release | semantic-release |
The Code of Conduct is adapted from the Contributor Covenant, version 1.4.