You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🌱 v5 to v6 top-up PRs must carry tide/merge-method-merge so Tide keeps v5 ancestry #19140
The v5 to v6 top-up PR #19100 was squash-merged by Tide into v6 (f4f3849, single parent), which dropped v5 ancestry. It was repaired by an -s ours merge PR #19118 (a20c827), which Tide could not merge ("nothing to commit"), so it was merged with gh pr merge --merge. Earlier top-ups #18341 and #18508 kept history only because they were plain-merged.
Fix: .github/workflows/v6-topup.yml should open (and refresh) the top-up PR with the tide/merge-method-merge label so Tide makes a merge commit, and src/docs/v5-sync-policy.md should state the rule, the repair recipe, and the post-merge ancestry check.
A hive agent asked to open a pull request that would close this issue, but it is covered by #19141 (@clubanderson). No PR was opened; the owner decides whether to proceed.
Activity
hivecommons-hive commentedon Nov 18, 2026
A hive agent asked to open a pull request that would close this issue, but it is covered by #19141 (@clubanderson). No PR was opened; the owner decides whether to proceed.