-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Updates codeowners file #164026
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
x-pack/test/security_solution_cypress/es_archives @elastic/security-engineering-productivity | ||
x-pack/test/security_solution_cypress/cli_config.ts @elastic/security-engineering-productivity | ||
x-pack/test/security_solution_cypress/config.ts @elastic/security-engineering-productivity | ||
x-pack/test/security_solution_cypress/runner.ts @elastic/security-engineering-productivity | ||
x-pack/test/security_solution_cypress/serverless_config.ts @elastic/security-engineering-productivity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW the reason why you were getting assigned as a code owners is because x-pack/test/security_solution_cypress @elastic/security-engineering-productivity
was below team-specific cypress folders like /x-pack/plugins/security_solution/common/api/detection_engine/rule_exceptions @elastic/security-detection-engine
in the CODEOWNERS file.
# Order is important; the last matching pattern takes the most
# precedence. ...
We could also move up the x-pack/test/security_solution_cypress @elastic/security-engineering-productivity
line so it's defined in the file above the team-specific folders. That way you'd own everything in x-pack/test/security_solution_cypress
except the team-owned folders. Which I'm not sure is what you want.
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Summary
Originally
security-engineering-productivity
team as owning thex-pack/test/security_solution_cypress/
folder since all the configuration related to the FTR server and archives lived there.After moving all the Cypress tests to that folder we missed updating the codeowners file to don't become a bottleneck on any small Cypress change. In this PR we are doing that by owning just those that might be relevant.