Repository navigation
ci(linux): add the Linux workflow and weekly dispatcher to main - #3441
Merged
Merged
Conversation
This was referenced Oct 16, 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.
Why
GitHub runs a schedule only from the default branch, and
mainhas no Linux workflow. So the Linux app's Monday run never fires: the full Docker matrix, the TLS suites and the fork drift checks.Change
build-linux.ymlcomes tomainunchanged fromlinux. Onmainitsdetectjob finds no Linux tree and every build job skips. On the schedule,weekly-dispatchstarts the workflow on the branch theLINUX_BRANCHvariable names,linuxwhen unset..claude/rules/ci.mdsays why the file is onmain.linux/merges intomain, the file is already identical, so that merge brings no conflict.Verified
actionlint and zizmor are clean, and every build job is gated on
detect.agent-docspasses.