Skip to content

merge: reconnect main ancestry into develop - #126

Merged
jubaoliang merged 5 commits into
developfrom
chore/reconnect-main-ancestry
Aug 1, 2026
Merged

merge: reconnect main ancestry into develop#126
jubaoliang merged 5 commits into
developfrom
chore/reconnect-main-ancestry

Conversation

@jubaoliang

Copy link
Copy Markdown
Collaborator

Summary

Important

Merge with a merge commit (not squash / rebase), or ancestry stays broken.

Test plan

  • After merge: git merge-base --is-ancestor origin/main origin/develop is true
  • Tree still identical to main

Made with Cursor

jubaoliang-tencent and others added 5 commits July 29, 2026 04:48
GITHUB_TOKEN-created GitHub Releases do not fire sibling release workflows.
Listen for Release workflow completion instead, and allow manual dispatch.

Co-authored-by: Cursor <cursoragent@cursor.com>
fix(ci): trigger Sync Main Into Develop via workflow_run
Auto Tag starts Release with GITHUB_TOKEN workflow_dispatch; in that
chain, workflow_run and release:published never started Sync. Cascade
explicitly after GitHub Release is created.
#124 squash-landed 0.9.17 content but left main outside develop's
ancestor graph; this empty merge restores merge-base checks for Sync.
@jubaoliang
jubaoliang merged commit ad00325 into develop Aug 1, 2026
3 checks passed
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.

2 participants