ci: stop running Phel job in fork; defer to phel-lang repo#15
Merged
Conversation
Re-comment the test-phel job to match jank-lang/clojure-test-suite. The Phel test run is now owned by phel-lang/phel-lang's run-clojure-test-suite.yml (with a nightly cron), so running it here duplicates work and forces this fork to diverge from upstream on CI. :phel reader conditionals in test files stay — they are content the phel-lang workflow consumes, and they're harmless to upstream readers.
This was referenced May 27, 2026
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
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.
Summary
test-pheljob in.github/workflows/ci.ymlto matchjank-lang/clojure-test-suiteupstream.run-clojure-test-suite.yml) which checks out this fork on every Phel push/PR and nightly at 06:00 UTC.Why
Per the Slack thread in
#clojure-test-suite(jasalt + jeaye): running Phel CI in the test-suite fork forces ongoing CI divergence from upstream and complicates sync. Pulling the suite from the Phel repo instead is simpler, lives next to Phel code, and is owned by Phel devs.`:phel` reader conditionals in test files stay — they are content the phel-lang workflow consumes, harmless to upstream readers, and a candidate to upstream eventually.
Test plan