mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-10 23:54:00 -05:00
b1d713ac55
* [AI] Resolve release-note PR links from base branch history The release-note generator recovered each note's PR number by reading the "(#NNNN)" suffix that GitHub appends to squash-merge commit subjects, searching HEAD — the release-notes/X.Y.Z branch it commits to. That branch only carries the note file *contents* (checked out from origin/release), not the commit history, so any note added to the release branch after it was cut (e.g. release cherry-picks) has no add-commit reachable from HEAD and silently loses its link. Search origin/master instead, where every note traces back to its original squash commit with the correct PR number. The release branch is unsuitable because "bring release branch up to date" squashes collapse original PRs. Verified across all 63 descriptively-named notes in the 26.7.0 set: 60 resolve identically to before, 3 previously-unlinked cherry-picks (#8301, #8335, #8339) are now linked, 0 regressions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * make the note human * Update upcoming-release-notes/release-notes-resolve-pr-link-from-master.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>