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

change the for loop to a new for range - part 1 #4996

Closed
wants to merge 1 commit into from

change the for loop to a new for range

d6732d8
Select commit
Loading
Failed to load commit list.
Closed

change the for loop to a new for range - part 1 #4996

change the for loop to a new for range
d6732d8
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 1, 2024 in 1s

1 potential rule

Rule: Auto-Merge on Approving Label and Changes Limited to docs/ Folder (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -files~=^(?!^docs).*
  • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • files~=^docs/
  • label=doc-merge
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Unit Tests
    • check-neutral = Unit Tests
    • check-skipped = Unit Tests
  • any of: [🛡 GitHub branch protection]
    • check-success = Basic Checks
    • check-neutral = Basic Checks
    • check-skipped = Basic Checks
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (discovery gossip devmode pluggable)
    • check-neutral = Integration Tests (discovery gossip devmode pluggable)
    • check-skipped = Integration Tests (discovery gossip devmode pluggable)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (gateway idemix pkcs11 configtx configtxlator)
    • check-neutral = Integration Tests (gateway idemix pkcs11 configtx configtxlator)
    • check-skipped = Integration Tests (gateway idemix pkcs11 configtx configtxlator)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (ledger)
    • check-neutral = Integration Tests (ledger)
    • check-skipped = Integration Tests (ledger)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (lifecycle)
    • check-neutral = Integration Tests (lifecycle)
    • check-skipped = Integration Tests (lifecycle)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (pvtdata)
    • check-neutral = Integration Tests (pvtdata)
    • check-skipped = Integration Tests (pvtdata)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (raft)
    • check-neutral = Integration Tests (raft)
    • check-skipped = Integration Tests (raft)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (sbe nwo msp)
    • check-neutral = Integration Tests (sbe nwo msp)
    • check-skipped = Integration Tests (sbe nwo msp)
  • any of: [🛡 GitHub branch protection]
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (pvtdatapurge)
    • check-neutral = Integration Tests (pvtdatapurge)
    • check-skipped = Integration Tests (pvtdatapurge)
  • any of: [🛡 GitHub branch protection]
    • check-success = Integration Tests (e2e smartbft)
    • check-neutral = Integration Tests (e2e smartbft)
    • check-skipped = Integration Tests (e2e smartbft)

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

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

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

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