ci: introduce ci/docker/env.sh #3774
Merged
Mergify / Summary
succeeded
Nov 25, 2024 in 5s
2 rules match and 8 potential rules
Rule: automatic merge (squash) on CI success (merge)
-
-closed
[📌 merge requirement] - all of:
-
label=automerge
-
label!=no-automerge
-
status-success=buildkite/agave
-
status-success=ci-gate
- any of:
-
-files~=^docs/
-
status-success=build & deploy docs
-
- any of:
-
-files~=(\.rs|Cargo\.toml|Cargo\.lock|\.github/scripts/cargo-clippy-before-script\.sh|\.github/workflows/cargo\.yml)$
- any of:
-
check-success=clippy-nightly (macos-latest)
-
check-success=clippy-nightly (macos-latest-large)
-
-
- any of:
-
-files~=(\.rs|Cargo\.toml|Cargo\.lock|cargo-build-sbf|cargo-test-sbf|ci/downstream-projects/run-spl\.sh|\.github/workflows/downstream-project-spl\.yml)$
- all of:
-
status-success=cargo-test-sbf (associated-token-account/program, associated-token-account/program-test)
-
status-success=cargo-test-sbf (feature-proposal/program)
-
status-success=cargo-test-sbf (governance/addin-mock/program, governance/program)
-
status-success=cargo-test-sbf (instruction-padding/program, token/program-2022, token/program-2022-test)
-
status-success=cargo-test-sbf (memo/program)
-
status-success=cargo-test-sbf (name-service/program)
-
status-success=cargo-test-sbf (single-pool/program)
-
status-success=cargo-test-sbf (stake-pool/program)
-
status-success=cargo-test-sbf (token-upgrade/program)
-
status-success=cargo-test-sbf (token/program)
-
-
-
-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] -
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
Rule: remove automerge label on CI failure (comment, label)
- all of:
-
#status-failure!=0
-
-merged
-
label=automerge
-
Rule: v2.0 feature-gate backport (backport)
-
label=feature-gate
-
label=v2.0
-
merged
[📌 backport requirement]
Rule: v2.0 non-feature-gate backport (backport)
-
label=v2.0
-
label!=feature-gate
-
merged
[📌 backport requirement]
Rule: v2.0 backport warning comment (comment)
-
label=v2.0
Rule: v2.1 feature-gate backport (backport)
-
label=feature-gate
-
label=v2.1
-
merged
[📌 backport requirement]
✅ Rule: v2.1 non-feature-gate backport (backport)
-
label!=feature-gate
-
label=v2.1
-
merged
[📌 backport requirement]
✅ Rule: v2.1 backport warning comment (comment)
-
label=v2.1
Rule: Reminder to update RPC clients for changes in rpc/
(comment)
- any of:
-
files~=^rpc-client-api/src/.*\.rs$
-
files~=^rpc/src/rpc\.rs$
-
files~=^rpc/src/rpc_pubsub\.rs$
-
Rule: Reminder to add Firedancer team to changes in programs/
and sdk/
(comment)
- any of:
-
files~=^programs/address-lookup-table/src/.*\.rs$
-
files~=^programs/bpf_loader/src/.*\.rs$
-
files~=^programs/compute_budget/src/.*\.rs$
-
files~=^programs/config/src/.*\.rs$
-
files~=^programs/loader-v4/src/.*\.rs$
-
files~=^programs/stake/src/.*\.rs$
-
files~=^programs/system/src/.*\.rs$
-
files~=^programs/vote/src/.*\.rs$
-
files~=^programs/zk-elgamal-proof/src/.*\.rs$
-
files~=^sdk/program/src/stake.*\.rs$
-
files~=^sdk/program/src/vote/.*\.rs$
-
3 not applicable rules
Rule: label changes from community (label)
-
author≠@core-contributors
-
author≠@monorepo-maintainers
-
author≠@monorepo-triage
-
author≠@monorepo-write
-
author≠dependabot[bot]
-
author≠github-actions[bot]
-
author≠mergify[bot]
Rule: request review for community changes (request_reviews)
-
#approved-reviews-by=0
-
#commented-reviews-by=0
-
author≠@core-contributors
-
author≠@monorepo-maintainers
-
author≠@monorepo-triage
-
author≠@monorepo-write
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
author≠dependabot[bot]
-
author≠github-actions[bot]
-
author≠mergify[bot]
Rule: label changes from monorepo-triage (label)
-
author≠@core-contributors
-
author≠@monorepo-maintainers
-
author≠@monorepo-write
-
author=@monorepo-triage
-
author≠dependabot[bot]
-
author≠github-actions[bot]
-
author≠mergify[bot]
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
Loading