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

chore(deps): update konflux references #2747

Merged
merged 1 commit into from
Nov 26, 2024

chore(deps): update konflux references

3034cd6
Select commit
Loading
Failed to load commit list.
Merged

chore(deps): update konflux references #2747

chore(deps): update konflux references
3034cd6
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 10, 2024 in 0s

3 rules match and 13 potential rules

⚠️ The pull request has been merged by @ezr-ondrej

✅ Rule: Remove outdated reviews (dismiss_reviews)

  • base=main

Rule: Request PR check re-run (comment, label)

  • all of:
    • all of:
      • #approved-reviews-by>=2
      • #changes-requested-reviews-by=0
    • any of:
      • -check-success=Lint
      • -check-success=ci.int.devshift.net PR build
    • base=main
    • label!=do not merge
    • label!=work in progress
    • updated-at<1 days ago

Rule: warn on conflicts (comment, label)

  • conflict

✅ Rule: remove conflict label if not needed (label)

  • -conflict

Rule: close stale pull request (close)

  • -closed
  • base=main
  • updated-at<14 days ago

✅ Rule: waiting for review (label)

  • #commented-reviews-by<2
  • -draft
  • created-at<1 days ago

Rule: remove waiting for review label if not needed (label)

  • #commented-reviews-by>=2
  • -draft

Rule: add bug fix label (label)

  • body~=(?m)^- \[[xX]\] Bug fix \(non-breaking change which fixes an issue\)

Rule: add new feature label (label)

  • body~=(?m)^- \[[xX]\] New feature \(non-breaking change which adds functionality\)

Rule: add documentation label (label)

  • body~=(?m)^- \[[xX]\] Documentation update

Rule: add test update label (label)

  • body~=(?m)^- \[[xX]\] Tests update

Rule: remove bug fix label (label)

  • body~=(?m)^- \[ \] Bug fix \(non-breaking change which fixes an issue\)

Rule: remove new feature label (label)

  • body~=(?m)^- \[ \] New feature \(non-breaking change which adds functionality\)

Rule: remove documentation label (label)

  • body~=(?m)^- \[ \] Documentation update

Rule: remove test update label (label)

  • body~=(?m)^- \[ \] Tests update

Rule: add ready label (label)

  • body~=(?m)^- \[[xX]\] I have added tests that prove my fix is effective or that my feature works
  • body~=(?m)^- \[[xX]\] I have commented my code, particularly in hard-to-understand areas
  • body~=(?m)^- \[[xX]\] I have made corresponding changes to the documentation
  • body~=(?m)^- \[[xX]\] I run make pre-commit to check fmt\/vet\/lint\/test-no-fdo
  • body~=(?m)^- \[[xX]\] New and existing unit tests pass locally with my changes

💖  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 for Dependabot pull requests (queue)

  • -closed [📌 queue requirement]
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue edge-api]
      • author~=^dependabot(|-preview)\[bot\]$
      • all of:
        • #approved-reviews-by>=2
        • #changes-requested-reviews-by=0
      • check-success=Lint
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
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