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.

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

Allow bot triggered PRs to run CI #4949

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

ev1yehor
Copy link
Contributor

@ev1yehor ev1yehor commented Jun 18, 2024

What does this PR do?

Allow bot triggered PRs to run CI

Why is it important?

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/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@ev1yehor ev1yehor requested a review from dliappis June 18, 2024 09:52
@ev1yehor ev1yehor self-assigned this Jun 18, 2024
Copy link
Contributor

mergify bot commented Jun 18, 2024

This pull request does not have a backport label. Could you fix it @ev1yehor? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@ev1yehor
Copy link
Contributor Author

/test

Copy link
Contributor

mergify bot commented Jun 18, 2024

This pull request does not have a backport label. Could you fix it @ev1yehor? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

1 similar comment
Copy link
Contributor

mergify bot commented Jun 18, 2024

This pull request does not have a backport label. Could you fix it @ev1yehor? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

Copy link

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ev1yehor ev1yehor marked this pull request as ready for review June 18, 2024 10:20
@ev1yehor ev1yehor requested a review from a team as a code owner June 18, 2024 10:20
@ev1yehor ev1yehor requested review from leehinman and pchila June 18, 2024 10:20
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 merged commit d557ebd into elastic:main Jun 18, 2024
11 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants