[release/6.0] Remove disableComponentGovernance parameter from jobs.yml (#8471)#8498
Merged
mmitche merged 1 commit intodotnet:release/6.0from Feb 22, 2022
Merged
Conversation
* Remove disableComponentGovernance parameter from jobs.yml
2 tasks
Contributor
Author
|
@mmitche this is the last one of these |
mmitche
approved these changes
Feb 22, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Remove disableComponentGovernance parameter from jobs.yml in release/6.0
cherry-pick of 64a7268
Customer Impact
Customers are not able to disable the component governance step in individual jobs because this property conflicts
Regression
No
Risk
Low. This change has been in main for a week now without issue
Workarounds
Customers can change their usage of
jobs.ymlto make multiple, individual calls tojob.ymlto disable these steps.