Repository navigation
Track upstream branches: omarchy-dev 4.0.0.r6807.g902fd8a, omarchy-settings-dev 4.0.0.r6807.g902fd8a - #788
Merged
Conversation
ryanrhughes
enabled auto-merge
October 4, 2026 01:54
ryanrhughes
force-pushed
the
auto/track-branches
branch
2 times, most recently
from
October 4, 2026 15:28
8c2b792 to
d8afc3c
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 4, 2026 19:46
d8afc3c to
56c5444
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 4, 2026 23:30
56c5444 to
a8e5fe7
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 5, 2026 06:04
a8e5fe7 to
d189f3b
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
6 times, most recently
from
October 7, 2026 09:06
2c91e49 to
d34248c
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 7, 2026 17:30
d34248c to
671e428
Compare
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 7, 2026 23:15
671e428 to
2678a6d
Compare
…ttings-dev 4.0.0.r6807.g902fd8a
ryanrhughes
force-pushed
the
auto/track-branches
branch
from
October 8, 2026 06:31
2678a6d to
963cbf1
Compare
Contributor
Publish succeeded → livePackages: omarchy-dev (x86_64, PR artifact); omarchy-dev (aarch64, PR artifact); omarchy-settings-dev (x86_64, PR artifact); omarchy-settings-dev (aarch64, PR artifact)
Some planned slots did not run because an earlier slot failed. |
ryanrhughes
added a commit
that referenced
this pull request
Oct 9, 2026
sync-upstream.yml, sync-rebuilds.yml and track-branches.yml each opened one batch PR, so one package with a failing build held back every other update in it (#788, #837). All three now group their changes with package-pr-groups.sh and hand them to package-prs.yml, which opens a PR per package and arms auto-merge. Packages pinned from the same upstream branch still share one. Green packages land on their own and only the failures stay open; a red PR conflicting with master, and each lane's old batch PR, get closed. sync-upstream.yml loses its human-merged lane: it now pushes with the PAT like the other two, so its builds start without an approval hold and its PRs auto-merge when green. min_release_age still quarantines fresh releases. Its approve job, approve-sync-push.cjs, and auto-merge-pr.cjs's exception for auto/sync-upstream go with it.
gentlemanSoup
pushed a commit
to gentlemanSoup/omarchy-pkgs
that referenced
this pull request
Oct 10, 2026
… back The branch tracker stalled omarchy-dev and omarchy-settings-dev twice in a week: - All ~50 auto_merge packages rode one PR, so omasnap-git's failing smoke suite kept the quattro pins unmerged from Oct 4 to Oct 8 (omacom#788). Each package now gets its own PR on auto/track-branches-<package>; packages pinned from the same branch share one, since they move in lockstep. A run closes tracker PRs that master has moved past, and the old single PR. - A branch tip younger than min_release_age held the whole branch, so a run that landed shortly after a quattro commit pinned nothing. The watch now falls back along first-parent history to the newest commit that has cleared the window, measured from clone time so siblings agree. - The every-2-hours schedule fired every 6 to 9 hours in practice; run it hourly.
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.
Automated pin of packages that follow a moving upstream branch
(
"auto_merge": truein.omarchy/package.json). Each package's_commitnow points at the branch tip. Fresh tips wait untiltheir commit timestamp is at least
min_release_ageold.This PR auto-merges once the build checks pass. A failing build
leaves it open; the next tracker run replaces it with the newer tip.