Skip to content

feat(discord/build): surface ethrex in /build client-el#156

Closed
barnabasbusa wants to merge 1 commit into
masterfrom
bbusa/build-add-ethrex-el
Closed

feat(discord/build): surface ethrex in /build client-el#156
barnabasbusa wants to merge 1 commit into
masterfrom
bbusa/build-add-ethrex-el

Conversation

@barnabasbusa
Copy link
Copy Markdown
Contributor

Summary

  • Add a small local override (extraClientsByType) in the build command so ethrex shows up in the /build client-el dropdown even though Cartographoor's remote data doesn't list it yet.
  • Inclusion is still gated on the workflow existing in eth-client-docker-image-builder (build-push-ethrex.yml — present), so unknown additions silently drop off rather than producing dead choices.
  • Treat the extras as known clients in GetToolWorkflows so ethrex doesn't double-list under /build tool.

Notes

  • Until Cartographoor catches up, ethrex's display name falls back to ethrex and the triggered-build embed uses the default panda thumbnail (no logo). The right long-term fix is to add ethrex upstream in Cartographoor's networks.json; this PR is the local stop-gap.

Test plan

  • /build client-el shows ethrex as an option in Discord
  • /build tool no longer lists ethrex
  • Triggering /build client-el client:ethrex dispatches build-push-ethrex.yml and the inline embed renders without error
  • Other EL clients (geth, reth, nethermind, besu, erigon, ethereumjs, nimbusel) still appear and dispatch correctly

Cartographoor's remote data does not list ethrex yet, but the
build-push-ethrex.yml workflow already exists upstream. Carry a small
local override so the EL dropdown picks it up and the tool list does not
double-list it.
@barnabasbusa barnabasbusa requested a review from mattevans as a code owner April 28, 2026 12:54
@skylenet
Copy link
Copy Markdown
Member

no

@skylenet skylenet closed this Apr 28, 2026
@barnabasbusa barnabasbusa deleted the bbusa/build-add-ethrex-el branch April 28, 2026 13:05
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.

2 participants