Skip to content
This repository was archived by the owner on Aug 17, 2026. It is now read-only.

chore(sync): upstream merge tooling + ci-zge - #16

Merged
joeshull merged 10 commits into
mainfrom
chore/upstream-sync-tooling
Jul 17, 2026
Merged

chore(sync): upstream merge tooling + ci-zge#16
joeshull merged 10 commits into
mainfrom
chore/upstream-sync-tooling

Conversation

@joeshull

@joeshull joeshull commented Jul 16, 2026

Copy link
Copy Markdown

Summary

Upstream-sync tooling for ZGEnergy/omp-dashboard (fork of BlackBeltTechnology/pi-agent-dashboard).

  • scripts/upstream-sync.sh: status | merge | verify | pr | ff-develop
  • Stable single PR head: sync/upstream-develop (force-with-lease); supersede only heads matching sync/upstream*
  • Protected-path auto --ours on merge conflicts
  • docs/upstream-sync.md policy
  • ci-zge / zge-gates (Node 22.22 + verify)
  • weekly upstream-sync workflow
  • deploy/install.sh default OMP_DASH_REF=main

Review notes

  • verify Gate 1 uses ephemeral HOME (upstream vitest isolation)
  • cmd_pr refuses main/develop/target; only sync/upstream* heads
  • PR body uses quoted heredoc (no backtick command substitution)

Test plan

  • scripts/upstream-sync.sh verify (Gate 0-2) locally
  • zge-gates green on this PR

Add scripts/upstream-sync.sh (status/merge/verify/pr), docs policy,
weekly upstream-sync workflow, and ci-zge focused gates so we can merge
BlackBelt develop without clobbering deploy/push/OMP surfaces. Default
install ref is main; README links the sync runbook.
@joeshull joeshull added the upstream-sync Automated or manual upstream merge label Jul 16, 2026
Joe added 2 commits July 16, 2026 16:23
Use stable branch sync/upstream-<ref>, force-with-lease each run, upsert
the same PR, and close older labeled/sync-head PRs as superseded so a
late review only has the latest merge to look at.
@joeshull

Copy link
Copy Markdown
Author

Updated per request: automation now keeps only one open upstream-sync PR (stable head , force-with-lease, closes superseded sync PRs).

@joeshull

Copy link
Copy Markdown
Author

Superseded by latest sync staging on sync/upstream-develop.

@joeshull joeshull closed this Jul 16, 2026
@joeshull joeshull reopened this Jul 16, 2026
@joeshull joeshull removed the upstream-sync Automated or manual upstream merge label Jul 16, 2026
@joeshull

Copy link
Copy Markdown
Author

Reopened. Supersede logic incorrectly closed this tooling PR because it used the \ label; only \ heads are superseded now.

Joe added 2 commits July 16, 2026 16:31
Gate 1 invoked vitest with real HOME, which upstream globalSetup
rejects. Match root npm test isolation and pass package vitest.config.
@joeshull joeshull changed the title chore(sync): upstream merge tooling + ci-zge chore(sync): upstream develop @ e75445fc Jul 16, 2026
@joeshull joeshull changed the title chore(sync): upstream develop @ e75445fc chore(sync): upstream merge tooling + ci-zge Jul 16, 2026
Joe added 5 commits July 16, 2026 16:46
Quote PR body heredoc to avoid backtick command substitution; refuse
force-with-lease on main/develop/target; recompute SYNC_BRANCH after
--ref; simplify workflow conflict-help echoes.
Precedence: --branch > env SYNC_BRANCH > sync/upstream-<ref>.
Capture SYNC_BRANCH_FROM_ENV before applying the default so an explicit
SYNC_BRANCH equal to the default name still wins over --ref.
Copy docs/upstream-sync-conflicts-YYYYMMDD.md to /tmp before abort and
restore onto the stable sync branch so the draft PR includes inventory.
Prevent SYNC_BRANCH=foo from force-publishing a non-sync head that
stale-PR closing would never supersede.
@joeshull
joeshull enabled auto-merge July 17, 2026 01:10
@joeshull
joeshull merged commit 59a8871 into main Jul 17, 2026
1 check passed
@joeshull
joeshull deleted the chore/upstream-sync-tooling branch July 17, 2026 01:12
joeshull pushed a commit that referenced this pull request Jul 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant