Skip to content

[dados mestres] changing zoneamento to only one resource #717

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

Open
patriciacatandi wants to merge 4 commits into
base: master
Choose a base branch
from
+5 −27

Merge branch 'master' into staging/dados_mestres

9472e03
Select commit
Loading
Failed to load commit list.
Open

[dados mestres] changing zoneamento to only one resource #717

Merge branch 'master' into staging/dados_mestres
9472e03
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 6, 2025 in 2s

2 potential rules

Rule: Automatic update for PRs (update)

  • #commits-behind > 0 [📌 update requirement]
  • #commits-behind>0
  • -closed
  • -closed [📌 update requirement]
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • -merged
  • label!=do-not-update
  • queue-position = -1 [📌 update requirement]

Rule: Warn author on conflicts (comment, label)

  • conflict
💖  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: Automatic merge to staging when there's nothing wrong with it (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>0
  • base=staging
  • check-success~=^pre-commit.ci
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • #commits-behind=0
  • -closed
  • -closed [📌 merge requirement]
  • -conflict
  • -conflict [📌 merge requirement]
  • -draft
  • -draft [📌 merge requirement]
  • -merged
  • check-success~=^GitGuardian
  • check-success~=^Lint
  • check-success~=^WIP
  • check-success~=^ubuntu
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = GitGuardian Security Checks
    • check-neutral = GitGuardian Security Checks
    • check-skipped = GitGuardian Security Checks
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint Dockerfile
    • check-neutral = Lint Dockerfile
    • check-skipped = Lint Dockerfile
  • any of: [🛡 GitHub branch protection]
    • check-success = WIP
    • check-neutral = WIP
    • check-skipped = WIP
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint Python
    • check-neutral = Lint Python
    • check-skipped = Lint Python
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