Problem description
The Release Progress Tracker currently creates a new update branch and pull request for each data refresh. This leaves older progress-update PRs open and makes it harder to tell which generated data change should be reviewed.
Expected action
Use a stable automation-owned branch and stable PR title for tracker data updates. If an open tracker PR already exists and the generated data changes, update that branch safely instead of opening another PR. If the generated tree is unchanged compared to the existing tracker PR branch, leave the PR unchanged.
Additional context
The branch update should avoid overwriting non-automation commits and should use a guarded force-with-lease update.
Problem description
The Release Progress Tracker currently creates a new update branch and pull request for each data refresh. This leaves older progress-update PRs open and makes it harder to tell which generated data change should be reviewed.
Expected action
Use a stable automation-owned branch and stable PR title for tracker data updates. If an open tracker PR already exists and the generated data changes, update that branch safely instead of opening another PR. If the generated tree is unchanged compared to the existing tracker PR branch, leave the PR unchanged.
Additional context
The branch update should avoid overwriting non-automation commits and should use a guarded force-with-lease update.