Avoid running the security pipeline on every PR #12
Conversation
This file contains 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
kmaziarz
force-pushed
the
kmaziarz/security-pipeline
branch
from
a37ab04
to
e9b53c8
Compare
AustinT
approved these changes
Jul 11, 2023
I can't be 100% sure, but if you look at the checks ran on this PR, the security pipeline (called |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 security pipeline defined in
azure_pipelines/code-security-analysis.ymlis scheduled to run weekly as required by Microsoft policy. However, it also seems to run on all PRs, which is unnecessary. This PR changes the pipeline's configuration to only do the scheduled runs and not run as part of CI.