Skip to content

merge-queue: embarking develop (c70bf95) and #4032 together#4037

Closed
mergify[bot] wants to merge 3 commits intodevelopfrom
mergify/merge-queue/564ff9d9f5
Closed

merge-queue: embarking develop (c70bf95) and #4032 together#4037
mergify[bot] wants to merge 3 commits intodevelopfrom
mergify/merge-queue/564ff9d9f5

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 21, 2022 •
edited
Loading

✨ Unexpected queue change: an external action moved the target branch head to 181c63e. The pull request #4032 has been re-embarked. ✨

Branch develop (c70bf95) and #4032 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #4032.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: core-utils-tests
    • check-skipped=ci/circleci: core-utils-tests
    • check-success=ci/circleci: core-utils-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: bedrock-go-tests
    • check-skipped=ci/circleci: bedrock-go-tests
    • check-success=ci/circleci: bedrock-go-tests
  • #approved-reviews-by>=2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success=pr-labeler
    • check-neutral=pr-labeler
    • check-skipped=pr-labeler
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: message-relayer-tests
    • check-neutral=ci/circleci: message-relayer-tests
    • check-skipped=ci/circleci: message-relayer-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: batch-submitter-tests
    • check-neutral=ci/circleci: batch-submitter-tests
    • check-skipped=ci/circleci: batch-submitter-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: bss-core-tests
    • check-neutral=ci/circleci: bss-core-tests
    • check-skipped=ci/circleci: bss-core-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: contracts-tests
    • check-neutral=ci/circleci: contracts-tests
    • check-skipped=ci/circleci: contracts-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: dtl-tests
    • check-neutral=ci/circleci: dtl-tests
    • check-skipped=ci/circleci: dtl-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: depcheck
    • check-neutral=ci/circleci: depcheck
    • check-skipped=ci/circleci: depcheck
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: gas-oracle-tests
    • check-neutral=ci/circleci: gas-oracle-tests
    • check-skipped=ci/circleci: gas-oracle-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: geth-tests
    • check-neutral=ci/circleci: geth-tests
    • check-skipped=ci/circleci: geth-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: indexer-tests
    • check-neutral=ci/circleci: indexer-tests
    • check-skipped=ci/circleci: indexer-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: integration-tests
    • check-neutral=ci/circleci: integration-tests
    • check-skipped=ci/circleci: integration-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: proxyd-tests
    • check-neutral=ci/circleci: proxyd-tests
    • check-skipped=ci/circleci: proxyd-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: replica-healthcheck-tests
    • check-neutral=ci/circleci: replica-healthcheck-tests
    • check-skipped=ci/circleci: replica-healthcheck-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: yarn-monorepo
    • check-neutral=ci/circleci: yarn-monorepo
    • check-skipped=ci/circleci: yarn-monorepo
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: contracts-bedrock-tests
    • check-neutral=ci/circleci: contracts-bedrock-tests
    • check-skipped=ci/circleci: contracts-bedrock-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: contracts-governance-tests
    • check-neutral=ci/circleci: contracts-governance-tests
    • check-skipped=ci/circleci: contracts-governance-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: contracts-periphery-tests
    • check-neutral=ci/circleci: contracts-periphery-tests
    • check-skipped=ci/circleci: contracts-periphery-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: op-bindings-build
    • check-neutral=ci/circleci: op-bindings-build
    • check-skipped=ci/circleci: op-bindings-build
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: devnet (with genesis contracts)
    • check-neutral=ci/circleci: devnet (with genesis contracts)
    • check-skipped=ci/circleci: devnet (with genesis contracts)

More informations about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the queue rules

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

---
pull_requests:
  - number: 4032
...

trianglesphere and others added 3 commits November 21, 2022 09:40
@trianglesphere
CI: Remove optional target from docker-publish step
324db7e 
The old nightlies used a partial build (which is the purpose of
the --target flag), but they were removed in PR #3330 (commit
f772f66).
@trianglesphere
ci: Split docker build & publish
80e17c0 
This splits the docker publish job into a build & publish job. They were
previously just steps. The build step uses docker save & circle workspaces
to provide the docker images to dependent jobs (like the publish & hive jobs).

This makes one change to the hive job to remove the docker.pull=true flag. This
is because it loads the image locally but in the case of an external contributor
the image will not be published. Docker will use the local image first & then
pull other images if they are not present.
@mergify
Merge of #4032
e1f2d0c
@changeset-bot
Copy link

changeset-bot bot commented Nov 21, 2022

⚠️ No Changeset found

Latest commit: e1f2d0c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mergify mergify bot closed this Nov 21, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Nov 21, 2022

This pull request has unexpected changes: an external action moved the target branch head to 181c63e. The whole train will be reset.

@mergify mergify bot deleted the mergify/merge-queue/564ff9d9f5 branch November 21, 2022 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@trianglesphere