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: README.md
-14Lines changed: 0 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,11 @@ jobs:
15
15
runs-on: ubuntu-latest
16
16
steps:
17
17
- uses: actions/checkout@v3
18
-
with:
19
-
fetch-depth: 0
20
18
- uses: wagoid/commitlint-github-action@v5
21
19
```
22
20
23
21
Alternatively, you can run on other event types such as `on: [push]`. In that case the action will lint the push event's commit(s) instead of linting commits from a pull request. You can also combine `push` and `pull_request` together in the same workflow.
24
22
25
-
**Note**: It's necessary that you specify the `fetch-depth` argument to `actions/checkout@v2` step. By default they fetch only latest commit of the branch, but we need more commits since we validate a range of commit messages.
26
-
27
23
## Inputs
28
24
29
25
You can supply these inputs to the `wagoid/commitlint-github-action@v5` step.
@@ -38,14 +34,6 @@ If the config file doesn't exist, [config-conventional](https://github.com/conve
38
34
39
35
Details on the configuration file can be found on [the commitlint website](https://commitlint.js.org/#/reference-configuration).
40
36
41
-
### `firstParent`
42
-
43
-
When set to true, we follow only the first parent commit when seeing a merge commit.
44
-
45
-
This helps to ignore errors in commits that were already present in your default branch (e.g. `master`) before adding conventional commit checks. More info in [git-log docs](https://git-scm.com/docs/git-log#Documentation/git-log.txt---first-parent).
0 commit comments