-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
chore: add build scripts to CODEOWNERS #28615
Conversation
This pull request does not have a backport label. Could you fix it @mdelapenya? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
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.
I will not say we, robots, are the owners but contributors, I understand there is no a well defined ownership but I prefer if the Beats team own those files.
I totally agree. I started with robots as a team, because there is no specific team nowadays. That's why I added @andresrc as reviewer, as we'd need to clarify who should attend PRs affecting those files. |
* chore: add build scripts to CODEOWNERS * chore: use Beats main team * chore: follow same path syntax (cherry picked from commit 2c927f0) # Conflicts: # .github/CODEOWNERS
* chore: add build scripts to CODEOWNERS * chore: use Beats main team * chore: follow same path syntax (cherry picked from commit 2c927f0) # Conflicts: # .github/CODEOWNERS
* chore: add build scripts to CODEOWNERS (#28615) * chore: add build scripts to CODEOWNERS * chore: use Beats main team * chore: follow same path syntax (cherry picked from commit 2c927f0) # Conflicts: # .github/CODEOWNERS * fix: resolve conflicts Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
* chore: add build scripts to CODEOWNERS (#28615) * chore: add build scripts to CODEOWNERS * chore: use Beats main team * chore: follow same path syntax (cherry picked from commit 2c927f0) # Conflicts: # .github/CODEOWNERS * fix: resolve conflicts Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
…urnalbeat-ci * upstream/master: (49 commits) [CI]: use the downstream packaging pipeline for branches/tags (elastic#28589) fix: use declarative style for complete variant of the elastic-agent (elastic#28526) x-pack/auditbeat/tracing: fix regexp for kprobe description line (elastic#28609) docs: Update `api_key` example on elasticsearch output (elastic#28606) chore: add build scripts to CODEOWNERS (elastic#28615) Osquerybeat: Fix host_processes missing cmdline arguments (elastic#28622) Add note about changes to regexp package in Golang (elastic#28616) CI: nightly/weekly builds for 7.x targeting 7.16 instead (elastic#28612) Osquerybeat: Fix extenstion unable to start on windows (elastic#28598) Osquerybeat: Return the query result count with the action response (elastic#28576) Agent: Allow custom response properties in the action response (elastic#28575) [Heartbeat] Only setuid in elastic-agent image (elastic#28577) Fix formatting of `mapStateJSON` and `layerListJSON` in dashboard assets (elastic#28530) CI: refactor the run e2e build (elastic#28502) Use fsnotify with long windows name-safe changes (elastic#28517) Remove unneeded mergify config backport: Add 7.16 branch (elastic#28560) Add proxy_url support to threatintel module's malwarebazaar fileset (elastic#28533) Osquerybeat: Implement host_users, host_groups, host_processes tables as a part of our osquery_extension. (elastic#28434) [Heartbeat] Make run_once syntax a boolean (elastic#28548) ...
* chore: add build scripts to CODEOWNERS * chore: use Beats main team * chore: follow same path syntax
What does this PR do?
It adds the Observability Robots as CODEOWNERS of the build packages under
dev-tools
package:mage, make and packaging
.I started with Robots, but I'd see it convenient to have a dedicated team for the build system:
beats-builders
,beats-operations
??Why is it important?
We would like to detect changes in those file so that any functional team would need a review from the specific team marked as CODEOWNER.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
Related issues