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 (e7c0a78), #3891 and #3957 together #3959

Closed
wants to merge 18 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 24, 2022

✨ Pull request #3957 which was ahead in the queue has been dequeued. The pull request #3957 has been re-embarked. ✨

Branch main (e7c0a78), #3891 and #3957 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #3957.
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 [🛡 GitHub branch protection]:
    • 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=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

oxarbitrage and others added 18 commits March 16, 2022 20:51
#3915)

* Update lightwalletd acceptance test for getblockchaininfo RPC

* Update some doc comments for network upgrades

* List network upgrades in order in the getblockchaininfo RPC

Also:
- Use a constant for the "missing consensus branch ID" RPC value
- Simplify fetching consensus branch IDs
- Make RPC type derives consistent
- Update RPC type documentation

* Make RPC type derives consistent

* Fix a confusing test comment
Co-authored-by: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com>
Co-authored-by: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com>
Co-authored-by: Janito Vaqueiro Ferreira Filho <janito.vff@gmail.com>
@mergify mergify bot closed this Mar 24, 2022
@mergify mergify bot deleted the mergify/merge-queue/main/3957 branch March 24, 2022 22:37
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.

3 participants