Skip to content

chore: skip upstream image workflow in fork - #11

Merged
DenisCarriere merged 1 commit into
masterfrom
fix/skip-upstream-publish-in-fork
Aug 3, 2026
Merged

chore: skip upstream image workflow in fork#11
DenisCarriere merged 1 commit into
masterfrom
fix/skip-upstream-publish-in-fork

Conversation

@DenisCarriere

@DenisCarriere DenisCarriere commented Aug 3, 2026

Copy link
Copy Markdown

Summary

  • run the inherited private Blockscout image publisher only in blockscout/blockscout
  • allow its dependent Blockscout E2E deployment job to skip automatically in forks
  • keep the Pinax Firehose image workflow as the fork publisher

Why

The inherited workflow targets a self-hosted runner labeled build and publishes to Blockscout-owned private images and deployment infrastructure. The Pinax fork has no such runner, leaving every push permanently queued even though the Pinax image workflow succeeds.

Validation

  • mix format completed in the pinned Elixir 1.19.4 / OTP 27 toolchain
  • workflow YAML parsed successfully
  • git diff --check passed
  • all PR checks passed after one retry of the inherited Explorer compiler-download mock flake
  • Explorer retry: 167 doctests, 1529 tests, 0 failures (1 excluded)
  • post-fix: stabilize V2 exchange rate channel test #10 expanded Blockscout matrix passed on rerun (95 jobs)
  • Pinax Firehose image publishing passed

Commit: a8fb80367

@DenisCarriere DenisCarriere changed the title ci: skip upstream image workflow in fork chore: skip upstream image workflow in fork Aug 3, 2026
@DenisCarriere
DenisCarriere merged commit 29d742a into master Aug 3, 2026
33 of 35 checks passed
@DenisCarriere
DenisCarriere deleted the fix/skip-upstream-publish-in-fork branch August 3, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant