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.

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

Allow bot triggered PRs to run CI #3638

Merged
merged 1 commit into from
Jun 18, 2024
Merged

Allow bot triggered PRs to run CI #3638

merged 1 commit into from
Jun 18, 2024

Conversation

ev1yehor
Copy link
Contributor

@ev1yehor ev1yehor commented Jun 18, 2024 •
edited
Loading

What is the problem this PR solves?

Allow bot triggered PRs to run CI

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

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

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

@ev1yehor ev1yehor added backport-skip Skip notification from the automated backport with mergify ci CI related tasks labels Jun 18, 2024
@ev1yehor ev1yehor requested a review from dliappis June 18, 2024 10:29
@ev1yehor ev1yehor self-assigned this Jun 18, 2024
@elastic-sonarqube Elastic SonarQube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@ev1yehor ev1yehor marked this pull request as ready for review June 18, 2024 11:47
@ev1yehor ev1yehor requested a review from a team as a code owner June 18, 2024 11:47
@ev1yehor ev1yehor merged commit 226806b into elastic:main Jun 18, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cmacknz cmacknz cmacknz approved these changes

@dliappis dliappis Awaiting requested review from dliappis

@AndersonQ AndersonQ Awaiting requested review from AndersonQ AndersonQ is a code owner automatically assigned from elastic/elastic-agent-control-plane

@michalpristas michalpristas Awaiting requested review from michalpristas michalpristas is a code owner automatically assigned from elastic/elastic-agent-control-plane

Assignees

@ev1yehor ev1yehor

Labels
backport-skip Skip notification from the automated backport with mergify ci CI related tasks
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ev1yehor @cmacknz