Skip to content

CI: siblings on the merged PR's branch after a merge; references downloaded by the tests - #70

Merged
JKRT merged 1 commit into
masterfrom
ci-merge-chains
Oct 23, 2026
Merged

JKRT merged 1 commit into
masterfrom
ci-merge-chains

Conversation

@JKRT

@JKRT JKRT commented Oct 23, 2026

Copy link
Copy Markdown
Owner
  • checkout-siblings: for a push, the branch of the pull request the commit was merged from is checked out first where it exists (lookup via gh api .../commits/<sha>/pulls; none or a failed lookup: master as before). A half-merged release chain then tests a consistent set; today all post-merge reds were version-skew (empty intersection between OMBackend@0.8.0 and project compatibility 0.7).
  • validateMSLModel downloads a missing reference with OMLibraryTesting's download_refs.sh; ci/fetch-msl-refs.sh (a grep of the test code) and its CI step removed.

Dry runs of the script on scratch repos and the lookup against today's merge commits check out as intended; msl 316/316 and core 325/325 locally. The integration workflow uses the action from master, so the push lookup first runs on the first merge after this one.

🤖 Generated with Claude Code

…nloaded by the tests

checkout-siblings looks up the pull request a pushed commit was merged from and
checks out the siblings at its branch where it still exists, so a half-merged
release chain tests a consistent set. validateMSLModel downloads a missing
reference (download_refs.sh); ci/fetch-msl-refs.sh and its grep removed.

Assisted-by: Claude Opus 5.5
@JKRT
JKRT merged commit dc86f38 into master Oct 23, 2026
6 checks passed
@JKRT
JKRT deleted the ci-merge-chains branch October 23, 2026 20:16
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