509b90841701b3b6347c7110fd5a2472bb7533c6
Bumps [github/super-linter](https://github.com/github/super-linter) from 4.8.5 to 4.8.7. - [Release notes](https://github.com/github/super-linter/releases) - [Changelog](https://github.com/github/super-linter/blob/main/docs/release-process.md) - [Commits](https://github.com/github/super-linter/compare/v4.8.5...v4.8.7) --- updated-dependencies: - dependency-name: github/super-linter dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Super Linter Reusable Workflow Examples
The GitHub Super-Linter project is a fantastic way to lint all your file types with a single GitHub Actions Workflow. A great way to implement it everywhere is to use GHA's Reusable Workflows (see below).
My video walkthrough of this repository
Features of this custom Super-Linter example
- All the features of Super-Linter in a Reusable Workflow
- Bonus: Optionally turn off non-DevOps linters (CSS, JS, HTML, etc.) when you want to ignore code (in my case it's to ignore sample code I stick in DevOps projects)
- Bonus: I added Job steps to correctly determine which branch to diff files with (in the case of having multiple release branches)
- Bonus: Lints only changed files on a PR, but lints all files on merge to main (or any release) branch
How to reuse this example as a Reusable Workflow
- Fork this repository for you to customize your linters
- Add a workflow to all your other repositories that calls your linter workflow using GitHub's "Reusable Workflow"
- Add something similar to this to those workflows:
---
name: Lint Code Base
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
call-super-linter:
# use Reusable Workflows to call my linter config remotely
# https://docs.github.com/en/actions/learn-github-actions/reusing-workflows
#FIXME: customize uri to point to your forked linter repository
uses: bretfisher/super-linter-workflow/.github/workflows/super-linter.yaml@main
How to run Super-Linter locally
Option 1: Use nektos/act to run an existing GitHub Action workflow on your local repository clone.
Option 2: Use Docker to run the Super-Linter image directly.