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

fix(pg): Avoid recompiling every single time we invoke the users script #1564

Merged
merged 1 commit into from
Mar 16, 2024

fix(pg): Avoid recompiling every single time we invoke the users script

24e1dcc
Select commit
Loading
Failed to load commit list.
Merged

fix(pg): Avoid recompiling every single time we invoke the users script #1564

fix(pg): Avoid recompiling every single time we invoke the users script
24e1dcc
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 16, 2024 in 1s

2 rules match and 6 potential rules

⚠️ The pull request has been merged by @RPate97

Rule: Automatic merge on approval (develop) (queue)

  • all of:
    • check-success=ci/circleci: executor-tests
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved=0
    • base=develop
    • check-success=ci/circleci: contracts-tests
    • check-success=ci/circleci: core-tests
    • check-success=ci/circleci: demo-tests
    • check-success=ci/circleci: plugins-tests
    • check-success=ci/circleci: yarn-monorepo
    • check-success=license/cla
    • label!=do-not-merge
    • label!=mergify-ignore
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

Rule: Add merge train label (comment, label)

  • queue-position >= 0

✅ Rule: Remove merge train label (label)

  • queue-position = -1

Rule: Ask to resolve conflict (comment, label)

  • conflict

✅ Rule: Remove conflicts label when conflicts gone (label)

  • -conflict

Rule: Notify author when added to merge queue (comment)

  • check-pending=Queue: Embarked in merge train

Rule: Notify author when merge queue failed (comment)

  • check-failure=Queue: Embarked in merge train

Rule: Nag changesets (comment)

  • all of:
    • -files~=^\.changeset/(.*)\.md
    • files~=\.((?<!\.spec\.)ts|js|sol)$

💖  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 on approval (main) (queue)

  • all of:
    • base=main
    • check-success=ci/circleci: executor-tests
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved=0
    • check-success=ci/circleci: contracts-tests
    • check-success=ci/circleci: core-tests
    • check-success=ci/circleci: demo-tests
    • check-success=ci/circleci: plugins-tests
    • check-success=ci/circleci: yarn-monorepo
    • check-success=license/cla
    • label!=do-not-merge
    • label!=mergify-ignore
  • -draft [📌 queue requirement]
  • 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