This repository was archived by the owner on Jan 6, 2025. It is now read-only.
Microsoft security and compliance tasks #301
Merged
Conversation
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
hawkticehurst
approved these changes
Dec 2, 2021
Member
hawkticehurst
left a comment
hawkticehurst
left a comment
There was a problem hiding this comment.
Beyond the comment I left it all looks great! Thank you!
Member
|
Oh actually one more thought, do you know if we should remove the GitHub actions pipeline that this is modeled after to adhere to security requirements? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Link to relevant issue
n/a
Description of changes
Updated Azure Pipelines tasks that split build and compliance steps into stages, with specific jobs that meet Microsoft internal security requirements.
Link to forked docs site