5
0
Fork 0
mirror of https://github.com/wagoid/commitlint-github-action.git synced 2025-11-07 08:06:54 +00:00
Lints Pull Request commits with commitlint
Find a file
Wagner Santos 550792f0ca feat: add results output
Resolves #39
2020-08-02 06:42:18 -03:00
.github/workflows ci: use node 12 when running tests 2020-07-03 15:56:43 -03:00
fixtures test: show coverage in CI tests 2019-12-09 20:29:48 -03:00
.commitlintrc.yml test: add second commitlint check using yml file instead of js 2019-10-08 13:19:58 -03:00
.dockerignore test: add tests for the action 2019-12-09 20:12:53 -03:00
.gitignore Initial commit 2019-10-01 18:29:56 -03:00
.prettierrc feat: add commitlint action 2019-10-04 00:17:29 -03:00
action.js feat: add results output 2020-08-02 06:42:18 -03:00
action.test.js feat: add results output 2020-08-02 06:42:18 -03:00
action.yml feat: add results output 2020-08-02 06:42:18 -03:00
CHANGELOG.md chore(release): publish 2020-07-03 16:08:10 -03:00
commitlint.config.js chore: add commitlint config file 2019-10-04 00:18:00 -03:00
Dockerfile perf: improve action pull speed by using an alpine image 2020-07-03 15:56:33 -03:00
entrypoint.sh feat: add support for additional dependencies 2020-02-22 09:41:32 -03:00
generateOutputs.js feat: add results output 2020-08-02 06:42:18 -03:00
gitCommits.js chore: obtain git hash too in the list of linted commits 2020-07-20 08:36:59 -03:00
jest.config.js test: add tests for the action 2019-12-09 20:12:53 -03:00
LICENSE Initial commit 2019-10-01 18:29:56 -03:00
package-lock.json feat: add results output 2020-08-02 06:42:18 -03:00
package.json feat: add results output 2020-08-02 06:42:18 -03:00
README.md feat: add results output 2020-08-02 06:42:18 -03:00
run.js test: add tests for the action 2019-12-09 20:12:53 -03:00
testUtils.js test: add tests for the action 2019-12-09 20:12:53 -03:00

Commitlint Github Action

Lints Pull Request commits with commitlint

Usage

Create a github workflow in the .github folder, e.g. .github/workflows/commitlint.yml:

name: Commitlint
on: [pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - uses: wagoid/commitlint-github-action@v1

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.

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.

Inputs

configFile

The path to your commitlint config file.

Default: commitlint.config.js

firstParent

When set to true, we follow only the first parent commit when seeing a merge commit.

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.

Default: true

failOnWarnings

Whether you want to fail on warnings or not.

Default: false

helpURL

Link to a page explaining your commit message convention.

default: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Outputs

results

The error and warning messages for each one of the analyzed commits. This is useful if you want to use the commitlint results in a JSON format in other jobs. See the documentation on how to read JSON information from outputs.

Below you can see an example text output together with its corresponding JSON output:

You have commit messages with errors

⧗   input: wrong message
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

⧗   input: chore: my message
⚠   body must have leading blank line [body-leading-blank]

⚠   found 0 problems, 1 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
[
  {
    "hash": "cb0f846f13b490c2fd17bd5ed0b6f65ba9b86c75",
    "message": "wrong message",
    "valid": false,
    "errors": ["subject may not be empty", "type may not be empty"],
    "warnings": [],
  },
  {
    "hash": "cb14483cbde23b61322ffb8d3fcdc87f514a3141",
    "message": "chore: my message\n\nsome context without leading blank line",
    "valid": true,
    "errors": [],
    "warnings": ["body must have leading blank line"],
  },
]

About extends in your config file

This is a Docker action, and was made like this so that you can run it with minimum setup, regardless of your repo's environment. It comes packed with the most famous shared configurations that you can use in your commitlint config's extends field:

Apart from the shared configurations that are included by default, you can also include extra dependencies for other configs and plugins that you want to use.

In order to do so, you can use NODE_PATH env var to make the action take those dependencies into account. Below is an example workflow that does that.

name: Commitlint
on: [pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - uses: actions/setup-node@v1
        with:
          node-version: '10.x'
      - run: npm install
      - name: Add dependencies for commitlint action
        # $GITHUB_WORKSPACE is the path to your repository
        run: echo "::set-env name=NODE_PATH::$GITHUB_WORKSPACE/node_modules"
      # Now the commitlint action will run considering its own dependencies and yours as well 🚀
      - uses: wagoid/commitlint-github-action@v1

💡 You can see other ways to install your dependencies (including private ones) in the Setup Node action's docs.