[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch circular-andouille-ee6tcx of the duplicated default from automatic merge queue, to test #152 before it merges into master. Pushing to this branch or closing this pull request removes #152 from the queue.

What this draft tests

Mergify checks that #152 still passes CI on top of master. CI runs on this draft's code, built in this order:

1. master at b2e2058
2. #152, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the duplicated default from automatic merge queue in the dashboard

What happens next

• Mergify merges #152 into master and closes this draft.

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: b2e20589d39fed043fdde62bd144e4753d99ab23
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 152
    scopes: []
scopes: []
...

Required conditions of queue rule duplicated default from automatic merge for merge

• check-success=test (build)
• check-success=test (docs-gnocchi-web)
• check-success=test (pep8)
• check-success=test (py310)
• check-success=test (py311)
• check-success=test (py312)

Required conditions to stay in the queue

• #approved-reviews-by>=1
  • Percent-encode resource ids in URL paths #152
• check-success=test (build)
  • Percent-encode resource ids in URL paths #152
• check-success=test (docs-gnocchi-web)
  • Percent-encode resource ids in URL paths #152
• check-success=test (pep8)
  • Percent-encode resource ids in URL paths #152
• check-success=test (py310)
  • Percent-encode resource ids in URL paths #152
• check-success=test (py311)
  • Percent-encode resource ids in URL paths #152
• check-success=test (py312)
  • Percent-encode resource ids in URL paths #152
• label!=work-in-progress
  • Percent-encode resource ids in URL paths #152