Scope Which Folders in /eng Trigger Core CI #14983
Merged
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
alzimmermsft
added
Client
weshaggard
reviewed
Sep 9, 2020
weshaggard
approved these changes
Sep 9, 2020
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.
This PR scopes which folders in
/engtrigger Core CI to run. Onlycode-quality-reports,pipelines, andscriptswill trigger Core CI to run. These folders are targeted to run Core CI as they have an affect on the entire repository, so a full build should be processed. Notably,versionsisn't included, this is due to changes made there will be localized to the SDKs affect. So, if a version change only updates Storage or Cosmos there is no need to run Core as well.