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

merge-queue: embarking main (4197704) and #3851 together #3857

Closed
wants to merge 10 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 12, 2022

🎉 This combination of pull requests has been checked successfully 🎉

Branch main (4197704) and #3851 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #3851.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue low for merge:

  • any of:
    • check-success=Clippy
    • check-neutral=Clippy
    • check-skipped=Clippy
  • any of:
    • check-success=Rustfmt
    • check-neutral=Rustfmt
    • check-skipped=Rustfmt
  • any of:
    • check-success=Test stable on macOS-latest
    • check-neutral=Test stable on macOS-latest
    • check-skipped=Test stable on macOS-latest
  • any of:
    • check-success=Test stable on ubuntu-latest
    • check-neutral=Test stable on ubuntu-latest
    • check-skipped=Test stable on ubuntu-latest
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • check-success=Test all
  • check-success=Test with fake activation heights
  • check-success=Test full validation sync from cached state
  • check-success=Test stable zebra-state with fake activation heights on ubuntu-latest
  • check-success=Test stable on ubuntu-latest
  • check-success=Test stable on macOS-latest
  • check-success=Coverage nightly
  • check-success=Clippy
  • check-success=Rustfmt

More informations about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@codecov
Copy link

codecov bot commented Mar 12, 2022

Codecov Report

Merging #3857 (9955274) into main (4197704) will decrease coverage by 0.03%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             main    #3857      +/-   ##
==========================================
- Coverage   78.82%   78.78%   -0.04%     
==========================================
  Files         295      295              
  Lines       33764    33788      +24     
==========================================
+ Hits        26613    26621       +8     
- Misses       7151     7167      +16     

@mergify
Copy link
Contributor Author

mergify bot commented Mar 12, 2022

The pull request #3851 is mergeable

@mergify mergify bot closed this Mar 12, 2022
@mergify mergify bot deleted the mergify/merge-queue/main/3851 branch March 12, 2022 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants