Skip to content

Adding Alert Processing Rule flexibility based on severity filters #666

Adding Alert Processing Rule flexibility based on severity filters

Adding Alert Processing Rule flexibility based on severity filters #666

Workflow file for this run

---
name: Code Review - Linting & Link Checks
on:
pull_request:
branches:
- main
workflow_dispatch: {}
jobs:
lint:
name: Lint code base
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Run github/super-linter
uses: github/super-linter@v7
env:
VALIDATE_ALL_CODEBASE: false
# Need to define main branch as default is set to master in super-linter
DEFAULT_BRANCH: main
# Enable setting the status of each individual linter run in the Checks section of a pull request
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# The following linter types will be enabled:
VALIDATE_JSON: true
VALIDATE_MARKDOWN: true
VALIDATE_POWERSHELL: true
VALIDATE_YAML: true
VALIDATE_BASH: true
VALIDATE_EDITORCONFIG: true
FILTER_REGEX_EXCLUDE: "(.*docs/themes/hugo-geekdoc/.*)|(.*tooling/.*)"
markdown-link-check:
name: Markdown Link Check
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Check links in markdown files
uses: gaurav-nelson/[email protected]
with:
config-file: ".github/linters/mlc_config.json"
use-verbose-mode: "yes"
use-quiet-mode: "yes"
check-modified-files-only: "yes"
base-branch: "main"