You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is a follow-up to #622, i.e. about cancelling previous workflow runs when a new push to a branch occurs.
One needs to be careful that only the mega-linter workflow is cancelled by assigning a unique concurrency group.
Example:
name: Mega-Linteron:
pull_request:
branches: [main]# Workflow can only run once per branch and any previous pending or in-progress runs are cancelled.concurrency:
group: ${{ github.ref }}-${{ github.workflow }}cancel-in-progress: trueenv:
APPLY_FIXES: allAPPLY_FIXES_EVENT: pull_requestAPPLY_FIXES_MODE: commitFILTER_REGEX_EXCLUDE: (\.github/workflows/)jobs:
lint:
# As usual...
Describe alternatives you've considered
Keep everything as is, which is also perfectly acceptable (so feel free to close this).
Is your feature request related to a problem? Please describe.
This is a follow-up to #622, i.e. about cancelling previous workflow runs when a new push to a branch occurs.
Describe the solution you'd like
GitHub actions directly offers a means to prevent concurrent workflow runs and concurrent job runs and to cancel any previous runs.
Advantages:
Disadvantages:
Example:
Describe alternatives you've considered
Keep everything as is, which is also perfectly acceptable (so feel free to close this).
Additional context
Links (same as above):
The text was updated successfully, but these errors were encountered: