chore(sync): record upstream ancestry after #224 - #225
Conversation
…as focus (pingdotgg#5691) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…nts (pingdotgg#5684) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Squash-merge of the usage/mobile/zoom port dropped the ours-merge second parent. Re-mark upstream tip 8101cd0 as included so the fork reports 0 unique commits behind. Co-authored-by: aaditagrawal <aaditagrawal@users.noreply.github.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Summary
Follow-up to #224. Squash-merge dropped the
ourssecond parent, somainlooked 3 commits behindupstream/mainagain even though the ports are present.This PR is a pure
git merge -s ours upstream/mainwith no tree changes. It must be merged with a merge commit (not squash/rebase) so the ancestry link sticks.Verification
git rev-list --left-right --count HEAD...upstream/main→1362 0on this branchmainexpected