molecule-ai/molecule-core
35
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity

chore: verify auto-sync main→staging post-#66 (empty trigger commit) #67

Merged
Ghost merged 1 commits from chore/verify-auto-sync-post-66 into main 2026-05-07 22:10:04 +00:00
Conversation 0 Commits 1 Files Changed -
Ghost commented 2026-05-07 22:09:33 +00:00
First-time contributor
Copy Link

Verification trigger for PR #66's rewrite of auto-sync-main-to-staging.yml.

Merging this empty commit to main will fire the new auto-sync workflow on the merge SHA. Expected behavior:

  • staging is already at main's tree post-#66 cleanup merge (commit 2679fdd0).
  • After this PR merges, main will advance to a new SHA; staging will be missing only this merge commit.
  • The new auto-sync workflow checks ancestor → falls through to needs_sync=true → fast-forwards staging to the new main tip → pushes directly via AUTO_SYNC_TOKEN.
  • Expected outcome: Auto-sync main → staging / sync-staging (push) GREEN within ~10s.

This is the second consecutive verification run (the first being the natural post-merge run of PR #66 itself, which surfaced the staging-side stale-workflow conflict resolved manually in commit 2679fdd0).

Close PR #52 after this merges (the same purpose, but PR #52 is behind main with old CodeQL workflow).

Verification trigger for PR #66's rewrite of `auto-sync-main-to-staging.yml`. Merging this empty commit to main will fire the new auto-sync workflow on the merge SHA. Expected behavior: - staging is already at `main`'s tree post-#66 cleanup merge (commit `2679fdd0`). - After this PR merges, main will advance to a new SHA; staging will be missing only this merge commit. - The new auto-sync workflow checks ancestor → falls through to `needs_sync=true` → fast-forwards staging to the new main tip → pushes directly via AUTO_SYNC_TOKEN. - Expected outcome: `Auto-sync main → staging / sync-staging (push)` GREEN within ~10s. This is the second consecutive verification run (the first being the natural post-merge run of PR #66 itself, which surfaced the staging-side stale-workflow conflict resolved manually in commit 2679fdd0). Close PR #52 after this merges (the same purpose, but PR #52 is behind main with old CodeQL workflow).
Ghost added 1 commit 2026-05-07 22:09:33 +00:00
chore: empty commit to verify auto-sync main→staging post-#66
All checks were successful
CodeQL / Analyze (${{ matrix.language }}) (go) (pull_request) Successful in 1s
Details
CodeQL / Analyze (${{ matrix.language }}) (javascript-typescript) (pull_request) Successful in 1s
Details
Retarget main PRs to staging / Retarget to staging (pull_request) Has been skipped
Details
CodeQL / Analyze (${{ matrix.language }}) (python) (pull_request) Successful in 1s
Details
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 5s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 6s
Details
CI / Detect changes (pull_request) Successful in 7s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 6s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 7s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 7s
Details
Runtime PR-Built Compatibility / detect-changes (pull_request) Successful in 7s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 2s
Details
CI / Platform (Go) (pull_request) Successful in 3s
Details
CI / Python Lint & Test (pull_request) Successful in 3s
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 3s
Details
CI / Canvas (Next.js) (pull_request) Successful in 4s
Details
CI / Canvas Deploy Reminder (pull_request) Has been skipped
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 4s
Details
Runtime PR-Built Compatibility / PR-built wheel + import smoke (pull_request) Successful in 3s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 4s
Details
f0664264cb
Ghost approved these changes 2026-05-07 22:09:57 +00:00
Ghost left a comment
Author
First-time contributor
Copy Link

Approved as verification trigger for #66. Empty commit; no code change.

Approved as verification trigger for #66. Empty commit; no code change.
Ghost merged commit 5efa92fbc6 into main 2026-05-07 22:10:04 +00:00
Ghost deleted branch chore/verify-auto-sync-post-66 2026-05-07 22:10:04 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Ghost
Labels
Clear labels   
tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

  
tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

  
tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

No Label
tier:high
tier:low
tier:medium
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#67
No description provided.
Delete Branch "chore/verify-auto-sync-post-66"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?