Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of chore: remove staff codeowners now that it requires mandatory review into release/1.20.x #22022

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #22020 to be assessed for backporting due to the inclusion of the label backport/1.20.

The below text is copied from the body of the original PR.


Description

The staff codeowners line items were added when the codeowners files were non-mandatory, to be used as a notification only. Now that the codeowners file requires mandatory review the spirit of the original change isn't correct anymore.


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/rboyer/remove-staff-codeowners/definitely-modern-locust branch from 148f060 to 6f79607 Compare December 18, 2024 22:37
@hc-github-team-consul-core hc-github-team-consul-core requested a review from a team as a code owner December 18, 2024 22:37
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@github-actions github-actions bot added the theme/contributing Additions and enhancements to community contributing materials label Dec 18, 2024
@rboyer rboyer merged commit f8a0bd0 into release/1.20.x Dec 19, 2024
103 checks passed
@rboyer rboyer deleted the backport/rboyer/remove-staff-codeowners/definitely-modern-locust branch December 19, 2024 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/contributing Additions and enhancements to community contributing materials
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants