Skip to content

this change will pass at first but will result in silent merge#9

Open
m3dwards wants to merge 2 commits into
masterfrom
250910-silent-merge-test-pr3
Open

this change will pass at first but will result in silent merge#9
m3dwards wants to merge 2 commits into
masterfrom
250910-silent-merge-test-pr3

Conversation

@m3dwards
Copy link
Copy Markdown
Owner

This PR should be fine as a PR but when it's merged into master it will cause a silent merge conflict with #5

Adds a periodic CI workflow that runs every 6 hours to detect silent
merge failures across all open PRs. For each PR, it fetches the
pre-built merge commit (pull/<n>/merge), runs a build and the tests,
and posts the result as a check run against the PR's head SHA. PRs
that have never been checked are prioritised (oldest first),followed
by those with the oldest existing check result.
@m3dwards m3dwards force-pushed the 250910-silent-merge-test-pr3 branch from 6686520 to 92820eb Compare May 28, 2026 17:48
@m3dwards m3dwards force-pushed the master branch 3 times, most recently from 393dc8a to 2ce4ae7 Compare June 1, 2026 20:01
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