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

[8.x](backport #6563) github-actions(pre-commit): detect merge conflicts and shebangs #6569

Merged
merged 2 commits into from
Feb 10, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 22, 2025

What does this PR do?

Use pre-commit with a subset of checks and run in the CI always.

Why is it important?

Similarly done at elastic/beats#42377

Help with detecting merge conflicts or shebang issues

Checklist

  • I have read and understood the pull request guidelines of this project.
  • 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?
  • ...

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

Sorry, something went wrong.

(cherry picked from commit 0bf9e06)
@mergify mergify bot added the backport label Jan 22, 2025
@mergify mergify bot requested review from a team as code owners January 22, 2025 08:34
@mergify mergify bot requested review from michel-laterman and removed request for a team January 22, 2025 08:34
@mergify mergify bot assigned v1v Jan 22, 2025
@mergify mergify bot requested a review from swiatekm January 22, 2025 08:34
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

@michalpristas michalpristas enabled auto-merge (squash) January 22, 2025 09:28
Copy link
Contributor Author

mergify bot commented Jan 27, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.x/pr-6563 upstream/mergify/bp/8.x/pr-6563
git merge upstream/8.x
git push upstream mergify/bp/8.x/pr-6563

Copy link
Contributor Author

mergify bot commented Jan 27, 2025

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

2 similar comments
Copy link
Contributor Author

mergify bot commented Feb 3, 2025

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

Copy link
Contributor Author

mergify bot commented Feb 10, 2025

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@v1v v1v disabled auto-merge February 10, 2025 11:48
@v1v v1v merged commit 3d9903f into 8.x Feb 10, 2025
8 checks passed
@v1v v1v deleted the mergify/bp/8.x/pr-6563 branch February 10, 2025 11:49
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.

None yet

3 participants