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

INT-B-19226 onboarding required fields fix for boat shipments #13567

Merged

Merge branch 'integrationTesting' into INT-B-19226-onboarding-require…

4f09407
Select commit
Loading
Failed to load commit list.
Merged

INT-B-19226 onboarding required fields fix for boat shipments #13567

Merge branch 'integrationTesting' into INT-B-19226-onboarding-require…
4f09407
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 28, 2024 in 0s

no rules match, no planned actions

⚠️ The pull request has been merged by @brooklyn-welsh


💖  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: merge using the merge queue (queue)

  • base=main
  • label=ready-to-merge
  • -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]
      • #approved-reviews-by>=2 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: build_migrations
        • check-neutral=ci/circleci: build_migrations
        • check-skipped=ci/circleci: build_migrations
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: build_app
        • check-neutral=ci/circleci: build_app
        • check-skipped=ci/circleci: build_app
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: build_storybook
        • check-neutral=ci/circleci: build_storybook
        • check-skipped=ci/circleci: build_storybook
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: build_tasks
        • check-neutral=ci/circleci: build_tasks
        • check-skipped=ci/circleci: build_tasks
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: check_tls_certificate_dp3
        • check-neutral=ci/circleci: check_tls_certificate_dp3
        • check-skipped=ci/circleci: check_tls_certificate_dp3
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: check_tls_certificate_prd
        • check-neutral=ci/circleci: check_tls_certificate_prd
        • check-skipped=ci/circleci: check_tls_certificate_prd
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: check_tls_certificate_stg
        • check-neutral=ci/circleci: check_tls_certificate_stg
        • check-skipped=ci/circleci: check_tls_certificate_stg
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: compile_app_client
        • check-neutral=ci/circleci: compile_app_client
        • check-skipped=ci/circleci: compile_app_client
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: compile_app_server
        • check-neutral=ci/circleci: compile_app_server
        • check-skipped=ci/circleci: compile_app_server
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: pre_test
        • check-neutral=ci/circleci: pre_test
        • check-skipped=ci/circleci: pre_test
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: pre_deps_golang
        • check-neutral=ci/circleci: pre_deps_golang
        • check-skipped=ci/circleci: pre_deps_golang
      • any of: [🛡 GitHub branch protection]
        • check-success=ci/circleci: pre_deps_yarn
        • check-neutral=ci/circleci: pre_deps_yarn
        • check-skipped=ci/circleci: pre_deps_yarn
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