You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,10 @@
11
11
1. Sign CLA (see [CLA](#cla) below).
12
12
1. Send us a pull request when you are done. We'll review your code, suggest any
13
13
needed changes, and merge it in.
14
-
1. Upon merge, a new release of the `@salesforce/plugin-packaging` plugin will be published to npmjs with a version bump corresponding to commitizen rules.
14
+
1. Upon merge, a new release of the `@salesforce/plugin-packaging` plugin will be published to npmjs with a version bump corresponding to the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).
15
+
- To increase the patch version, make sure that at least 1 commit message starts with "fix:"
16
+
- To increase the minor version, make sure that at least 1 commit message starts with "feat:"
17
+
- To bump the major version, please work with the CLI team.
1. Commit staged files with helpful commit message: `git commit`
37
+
1. Commit staged files with helpful commit message following the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).: `git commit`
38
+
- See [When you are ready to commit](#When-you-are-ready-to-commit)
37
39
1. Push commit(s) to remote: `git push -u origin <branch_name>`
38
40
1. Create a pull request (PR) using the GitHub UI [here](https://github.com/salesforcecli/plugin-packaging).
39
41
@@ -77,6 +79,15 @@ sf plugins
77
79
sf package create --help
78
80
```
79
81
82
+
## When you are ready to commit
83
+
84
+
If you want your changes to be published to npmjs, your commit messages must follow the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).
85
+
86
+
- To increase the patch version, make sure that at least 1 commit message starts with "fix:"
87
+
- To increase the minor version, make sure that at least 1 commit message starts with "feat:"
88
+
- To bump the major version, please work with the CLI team.
89
+
If you'd like a review from a CLI developer, please tag us in Slack or in the PR.
0 commit comments