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.

Sign up for GitHub

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

Jump to bottom

doc: Update usage.rst #337

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Update usage.rst removed consuming messages instructions

16d19fc
Select commit
Loading
Failed to load commit list.
Open

doc: Update usage.rst #337

Update usage.rst removed consuming messages instructions
16d19fc
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Apr 25, 2024 in 2s

1 potential rule

Rule: default (queue)

  • #changes-requested-reviews-by=0
  • approved-reviews-by=@fedora-infra/fedora-messaging-maintainers
  • status-success=DCO
  • status-success=Integration tests (py310-integration)
  • status-success=Integration tests (py311-integration)
  • status-success=Integration tests (py312-integration)
  • status-success=Integration tests (py38-integration)
  • status-success=Integration tests (py39-integration)
  • status-success=Misc tests (checks)
  • status-success=Unit tests (py310-unittest)
  • status-success=Unit tests (py311-unittest)
  • status-success=Unit tests (py312-unittest)
  • status-success=Unit tests (py38-unittest)
  • status-success=Unit tests (py39-unittest)
  • -draft
  • -draft [📌 queue requirement]
  • label!=no-mergify
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

1 not applicable rule

Rule: default-from-fedora-messaging-team (queue)

  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • author=@fedora-infra/fedora-messaging-maintainers
  • status-success=DCO
  • status-success=Integration tests (py310-integration)
  • status-success=Integration tests (py311-integration)
  • status-success=Integration tests (py312-integration)
  • status-success=Integration tests (py38-integration)
  • status-success=Integration tests (py39-integration)
  • status-success=Misc tests (checks)
  • status-success=Unit tests (py310-unittest)
  • status-success=Unit tests (py311-unittest)
  • status-success=Unit tests (py312-unittest)
  • status-success=Unit tests (py38-unittest)
  • status-success=Unit tests (py39-unittest)
  • -draft
  • -draft [📌 queue requirement]
  • label!=no-mergify
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]
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

View more details on Mergify