Clarify permissions in call-super-linter.yaml #13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| --- | ||
| # template source: https://github.com/bretfisher/super-linter-workflow/blob/main/templates/call-super-linter.yaml | ||
| name: Lint Code Base | ||
| on: | ||
| push: | ||
| branches: [main] | ||
| pull_request: | ||
| jobs: | ||
| call-super-linter: | ||
|
Check failure on line 13 in .github/workflows/call-super-linter.yaml
|
||
| name: Call Super-Linter | ||
| # all other permissions not listed are set to `none` | ||
| # https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#permissions | ||
| permissions: | ||
| contents: read # clone the repo to lint | ||
| statuses: none #read/write to repo custom statuses | ||
| ### use Reusable Workflows to call my workflow remotely | ||
| ### https://docs.github.com/en/actions/learn-github-actions/reusing-workflows | ||
| ### you can also call workflows from inside the same repo via file path | ||
| #FIXME: customize uri to point to your own linter repository | ||
| uses: bretfisher/super-linter-workflow/.github/workflows/reusable-super-linter.yaml@main | ||
| ### Optional settings examples | ||
| # with: | ||
| ### For a DevOps-focused repository. Prevents some code-language linters from running | ||
| ### defaults to false | ||
| # devops-only: false | ||
| ### A regex to exclude files from linting | ||
| ### defaults to empty | ||
| # filter-regex-exclude: html/.* | ||
