Fix Super-Linter to run on pull requests to all branches #10035
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Super-Linter workflow was only running on pull requests targeting the
main
branch, which caused linting issues to be discovered late in the release process. When creating release branches (likedotnet10-p7
) and merging area-specific pull requests into those branches, the linting checks were bypassed, leading to a accumulation of issues that were only caught during the final merge to main.This change updates the Super-Linter workflow configuration to run on pull requests to all branches by changing:
to:
This matches the pattern already used by the
markdown-link-check.yml
workflow and ensures that linting runs consistently across all pull requests, regardless of the target branch.With this fix, area-specific pull requests (like
dotnet10-p7-libraries
targetingdotnet10-p7
) will now trigger the Super-Linter, catching issues early in the development process rather than during the final merge.Fixes #10034.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.