ci: adopt the rework GitHub Actions on main so PR checks register - #18
Merged
Conversation
Lands the workflow set the engine rework introduced (CI.yml test matrix + docs, Runic.yml formatter, refreshed CompatHelper/TagBot) and drops the superseded Tests.yml/Formatter.yml/Documenter.yml. Until these live on the default branch, Actions does not recognize them, so PRs targeting main (e.g. #17) report no checks. Merging this registers them.
thevolatilebit
added a commit
that referenced
this pull request
Jul 22, 2026
Empty commit to emit a pull_request synchronize event. The CI/Runic workflows were registered on the default branch in #18, but an already-open PR gets no event when its base branch changes — only on commits to its own head. This nudges the checks to run.
thevolatilebit
added a commit
that referenced
this pull request
Jul 22, 2026
Main carried a small 2024 readme edit that conflicted with the rework's full readme rewrite, leaving PR #17 unmergeable — and an unmergeable PR produces no merge ref, so no pull_request checks run. Resolve readme.md in favor of the rework version. Main's only other delta (the CI workflows from #18) is already identical here, so this merge is otherwise a no-op.
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.
Why
PRs into
main(e.g. #17) currently report no checks. The engine rework renamed/replaced the workflow set (Tests.yml→CI.yml,Formatter.yml→Runic.yml,Documenter.ymlfolded intoCI.yml), but those new files have never existed on the default branch. GitHub Actions registers workflows from the default branch, so it doesn't recognize the new ones — and the old ones they replaced are gone from the PR head, leaving nothing to trigger.What
Lands only
.github/workflows/, bringingmainto the rework workflow set:CI.yml(version × OS test matrix + nightly + downgrade-compat + docs build/deploy)Runic.yml(formatter check)CompatHelper.yml,TagBot.ymlTests.yml,Formatter.yml,Documenter.ymlFiles are byte-identical to the workflow set on the rework branch. Merging this fires
CI.yml'spush: [main]trigger, which registers the workflows so every subsequent PR shows checks.Note
The test matrix will run against main's current (pre-rework) code on merge and may go red there — that is expected; the purpose of this PR is to register the workflows. It goes green once the rework engine lands.