This action will run PHPCS
together with reviewdog to create a report for your pull requests. It was created by modifying action-phpcs-wordpress
The Drupal rulesets are bundled and made available to phpcs
.
inputs:
github_token:
description: 'GITHUB_TOKEN'
default: '${{ github.token }}'
workdir:
description: 'Working directory relative to the root directory.'
default: '.'
### Flags for reviewdog ###
level:
description: 'Report level for reviewdog [info,warning,error]'
default: 'error'
tool_name:
description: 'Tool name to use for reviewdog reporter'
default: 'phpcs'
reporter:
description: 'Reporter of reviewdog command [github-pr-check,github-check,github-pr-review].'
default: 'github-pr-check'
filter_mode:
description: |
Filtering mode for the reviewdog command [added,diff_context,file,nofilter].
Default is added.
default: 'added'
fail_on_error:
description: |
Exit code for reviewdog when errors are found [true,false]
Default is `false`.
default: 'false'
reviewdog_flags:
description: 'Additional reviewdog flags'
default: ''
### Flags for phpcs-drupal ###
phpcs_args:
description: 'Additional PHPCS flags'
default: '.'
phpcs_extensions:
description: 'File extensions to check'
default: 'php,module,inc,install,test,profile,theme,css,info,txt,md,yml'
phpcs_ignore:
description: 'Files to ignore'
default: 'node_modules,bower_components,vendor'
phpcs_standard:
description: 'Coding standard for PHPCS to use when checking files'
default: 'Drupal'
name: reviewdog
on: [pull_request]
jobs:
linter_name:
name: runner / phpcs
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: acrollet/action-phpcs-drupal@v1
with:
github_token: ${{ secrets.github_token }}
# Change reviewdog reporter if you need [github-pr-check,github-check,github-pr-review].
reporter: github-pr-review
# Change reporter level if you need.
# GitHub Status Check won't become failure with warning.
level: warning
The following sniffs are currently available. You can configure the standard(s) used by using the phpcs_standard
input setting. By default, WordPress
is used.
You can bump version on merging Pull Requests with specific labels (bump:major,bump:minor,bump:patch). Pushing tag manually by yourself also work.
This action updates major/minor release tags on a tag push. e.g. Update v1 and v1.2 tag when released v1.2.3. ref: https://help.github.com/en/articles/about-actions#versioning-your-action
This reviewdog action template itself is integrated with reviewdog to run lints which is useful for Docker container based actions.
Supported linters:
This repository uses haya14busa/action-depup to update reviewdog version.