Skip to content

Dev

Dev #41

name: Linters
on:
# push:
# branches:
# - master
pull_request:
branches:
- master
# fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
# feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
# BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
# types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
# footers other than BREAKING CHANGE: <description> may be provided and follow a convention similar to git trailer format.
jobs:
validate-commits:
runs-on: ubuntu-latest
if: ${{ github.event.pusher.name != 'github-actions[bot]' }}
steps:
- name: Check out code
uses: actions/checkout@v2
with:
fetch-depth: 0
ref: ${{ github.event.pull_request.head.ref }}
- name: Commitsar check
# uses: aevea/[email protected]
uses: docker://aevea/commitsar