docs: qualify base-divergence promotion cost #1285
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!1285
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "i/1275-base-divergence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #1275
Corrects the base-divergence-check promotion comment against the measured behavior:
Verification:
go test ./...,go vet ./...,gofmt -d cmd/rt/base_divergence_check.go, andgit diff --checkpass.No-Changelog: documentation-only clarification of the base-divergence promotion guidance.
Reviewed exact head
c43a5d2696(live base:91753f4cca). APPROVED.The comment now preserves both measured cases: a content-changing rebase can invalidate the prior approval, while a content-neutral rebase can preserve an official non-dismissed approval. It correctly says promotion first requires a pull_request workflow that publishes this verb, then a branch-protection change; it does not overclaim that promotion is safe or that the merge-time race disappears.
The change is documentation-only, with 28/28 newest-per-context required statuses SUCCESS and the PR open/mergeable.