ci: run tests and avoid duplicate PR+push triggers - #28
Merged
Merged
Conversation
dominicletz
force-pushed
the
ci/dedupe-and-run-tests
branch
2 times, most recently
from
August 10, 2026 17:57
da252c3 to
4d849a9
Compare
1. Scope `push` to the protected branches (main, develop) and leave `pull_request` unscoped. Without this, pushing a branch and opening a PR on the same commit triggered the job twice (once from the push, once from the pull_request event). 2. Install Foundry (anvil) in the job and uncomment `mix test`. The full test suite starts a local anvil chain via TestHelper.restart_chain/0, so anvil needs to be on PATH. The job is renamed from 'Build and lint' to 'Build, lint, and test' to reflect the broader scope.
dominicletz
force-pushed
the
ci/dedupe-and-run-tests
branch
from
August 10, 2026 18:08
4d849a9 to
c31c39c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two updates to
.github/workflows/ci.yml:De-duplicate PR + push triggers.
on: [push, pull_request]made the job fire twice on the same commit when a branch was pushed
and then opened as a PR (once for the push, once for the pull request).
pushis now scoped to the protected branches (main,develop);every PR to any branch is covered by the un-scoped
pull_requesttrigger.
Run the test suite in CI. The job installs Foundry (anvil) — see
the comment in the step for why we go via the GitHub release tarball
instead of
foundryupfrom foundry.paradigm.xyz (its bootstrapperis broken on the current Ubuntu runner image).
The actual tests run are
mix test.turnandmix test.nat— themix aliases defined in
mix.exsfor isolated CI-style runs. Theydon't need anvil, forge, gitignored PEM fixtures, or WireGuard kernel
privileges, so they're the realistic baseline today.
Running the full
mix testin CI is tracked separately because thesuite additionally depends on:
test/pems/*.pemfixtures that are*.pem-gitignored with noin-repo generator,
forgedeploying Solidity contracts viaChains.Anvil,CAP_NET_ADMIN) for the@requires_wireguard-tagged tests.