Skip to content

[8.19](backport #5112) github(codeowners): robots-ci can review .github/workflows only#5119

Merged
v1v merged 2 commits into8.19from
mergify/bp/8.19/pr-5112
Jul 9, 2025
Merged

[8.19](backport #5112) github(codeowners): robots-ci can review .github/workflows only#5119
v1v merged 2 commits into8.19from
mergify/bp/8.19/pr-5112

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Jul 9, 2025

What is the problem this PR solves?

// Please do not just reference an issue. Explain WHAT the problem this PR solves here.

How does this PR solve the problem?

This should help with letting the teams own other files under the .github folder

How to test this PR locally

Design Checklist

  • I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
  • I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
  • I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

  • 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/fragments using the changelog tool

Related issues


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

(cherry picked from commit 34a1057)

# Conflicts:
#	.github/CODEOWNERS
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jul 9, 2025
@mergify mergify bot requested a review from a team as a code owner July 9, 2025 09:07
@mergify mergify bot added the backport label Jul 9, 2025
@mergify mergify bot requested a review from ycombinator July 9, 2025 09:07
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Jul 9, 2025
@mergify mergify bot requested a review from pchila July 9, 2025 09:07
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Jul 9, 2025

Cherry-pick of 34a1057 has failed:

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

You are currently cherry-picking commit 34a1057.
  (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 Jul 9, 2025
@prodsecmachine
Copy link
Copy Markdown

prodsecmachine commented Jul 9, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@v1v v1v removed the conflicts There is a conflict in the backported pull request label Jul 9, 2025
@v1v v1v merged commit 0896798 into 8.19 Jul 9, 2025
7 checks passed
@v1v v1v deleted the mergify/bp/8.19/pr-5112 branch July 9, 2025 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants