- Please read our Code of Conduct.
- Please create a new issue here before starting any work so that we can also offer suggestions or let you know if there is already an effort in progress.
- Fork this repository (external contributors) or branch off
main(committers). - Create a topic branch based on
main. This is recommended but not required if contributing using a fork. - Edit the code in your fork/branch.
- Sign the Salesforce CLA.
- The CLI team will review your pull request and provide feedback.
- Once merged, a new release of
@salesforce/cliwill be published to npm.
External contributors are required to sign a Contributor License Agreement. You can do so by going to https://cla.salesforce.com/sign-cla.
- We work in branches off of
main. - Our release (aka. production) branch is
main. - Our work happens in topic branches (feature and/or bug-fix).
- Feature as well as bug-fix branches are based on
main - Branches should be kept up-to-date using
rebase
- Feature as well as bug-fix branches are based on
- Develop features and bug fixes in topic branches off main, or forks.
- Topic branches can live in forks (external contributors) or within this repository (internal contributors).
- When creating topic branches in this repository please prefix with
<initials>/. For example:mb/refactor-tests.
- When creating topic branches in this repository please prefix with
- Use conventional commits to drive semver versioning. Examples:
chore: my chore message--> No releasefix: my fix message--> Patch releasefeat: my feat message--> Minor release
- PRs will be reviewed and merged by the CLI team.