8000 [8.18](backport #43313) Update CODEOWNERS by mergify[bot] · Pull Request #44729 · elastic/beats · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[8.18](backport #43313) Update CODEOWNERS #44729

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Jun 11, 2025
Merged

[8.18](backport #43313) Update CODEOWNERS #44729

merged 3 commits into from
Jun 11, 2025

Conversation

mergify[bot]
Copy link
Contributor
@mergify mergify bot commented Jun 10, 2025

Proposed commit message

We are deprecating the GH team called ingest-eng-prod:

For such, we are now using two GH teams:

  • @elastic/observablt-ci
  • @elastic/observablt-ci-contractors

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #43313 done by [Mergify](https://mergify.com).

@v1v @mergify
8000 Update CODEOWNERS (#43313)
02e268e 
We are deprecating the GH team called `ingest-eng-prod`:

For such, we are now using two GH teams:
- @elastic/observablt-ci
- @elastic/observablt-ci-contractors

(cherry picked from commit 0c4e2d0)

# Conflicts:
#	.github/CODEOWNERS
@mergify mergify bot requested a review from a team as a code owner June 10, 2025 14:16
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jun 10, 2025
@mergify Mergify
Copy link
Contributor Author
mergify bot commented Jun 10, 2025

Cherry-pick of 0c4e2d0 has failed:

On branch mergify/bp/8.18/pr-43313
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit 0c4e2d0af.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/CODEOWNERS

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify bot assigned v1v Jun 10, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 10, 2025
@mergify mergify bot mentioned this pull request Jun 10, 2025
Merged
6 tasks
@botelastic
Copy link
botelastic bot commented Jun 10, 2025

This pull request doesn't have a Team:<team> label.

v1v
v1v reviewed Jun 10, 2025
View reviewed changes
v1v
v1v reviewed Jun 10, 2025
View reviewed changes
v1v
v1v reviewed Jun 10, 2025
View reviewed changes
v1v
v1v reviewed Jun 10, 2025
View reviewed changes
@v1v v1v removed the conflicts There is a conflict in the backported pull request label Jun 10, 2025
@v1v v1v merged commit 9ea3d28 into 8.18 Jun 11, 2025
9 checks passed
@v1v v1v deleted the mergify/bp/8.18/pr-43313 branch June 11, 2025 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@v1v v1v v1v approved these changes

Assignees

@v1v v1v

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@v1v
0