This repository has been archived by the owner on Nov 6, 2023. It is now read-only.
[SCM ADMIN] Adding/Updating GUS aware code owners info @W-13958158 #96
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is automatically generated by the SCM Admins to update the GUS Aware Codeowner file for the Repository. The repo owners have been informed by the security team about the upcoming PR scheduled for Auguest 19th, 2023. This notice is in case ownership information isn't added by August 18, 2023.
We kindly ask the repo owners to review the PR, make corrections if any ownership information is inaccurate, and complete the merge process by August 24, 2023. If no action is taken by that date, the PRs will be automatically merged.
For any inquiries, feel free to consult the Repo Lifecycle Management FAQs or the SCM Repo policies and Cleanup . In case your question isn't addressed there, you can ask it on the Slack channel #repo-lifecycle-management-support.