@@ -12,7 +12,7 @@ Add [commitizen][cz] incredibly fast into your project!
12
12
13
13
Are you using [ conventional commits] [ cc ] and [ semver] [ semver ] ?
14
14
15
- Then you are ready to use this github action, the only thing you'll need is the
15
+ Then you are ready to use this github action! The only thing you'll need is the
16
16
` .cz.toml ` file in your project.
17
17
18
18
## Usage
@@ -87,23 +87,23 @@ jobs:
87
87
| --------- | --------------- |
88
88
| `version` | The new version |
89
89
90
- Additionally, the new version is also availble as an environment variable under `REVISION`.
90
+ Additionally, the new version is also available as an environment variable under `REVISION`.
91
91
92
92
# # Troubleshooting
93
93
94
94
# ## Other actions are not triggered when the tag is pushed
95
95
96
- This problem occurs because `secrets.GITHUB_TOKEN` does not trigger other
96
+ This problem occurs because `secrets.GITHUB_TOKEN` do not trigger other
97
97
actions [by design][by_design].
98
98
99
- To solve it you must use a personal access token in the checkout and the commitizen steps.
99
+ To solve it, you must use a personal access token in the checkout and the commitizen steps.
100
100
101
101
Follow the instructions in [commitizen's documentation][cz-docs-ga]
102
102
103
103
# # I'm not using conventional commits, I'm using my own set of rules on commits
104
104
105
- If your rules can be parsed then you can build your own commitizen rules, you can
106
- create a new commitizen python package or you can describe it on the `toml` conf itself.
105
+ If your rules can be parsed, then you can build your own commitizen rules,
106
+ create a new commitizen python package, or you can describe it on the `toml` config itself.
107
107
108
108
[Read more about customization][cz-custom]
109
109
0 commit comments