cockroachdb / cockroachdb/cockroach
release: post notices in PRs that don't make a release branch cut
Open
A-release
C-cleanup
T-code-sys
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
It's a common problem to merge a PR thinking it would make it into the next release, but the merge doesn't make the branch cut and the author is unaware.
A bot should post on all PRs that merge right after the branch cut (say for ~1 week) explaining that the change is not on the release branch and if it needs to be there it should be backported.
Jira issue: CRDB-53125
Epic RE-35
Contributor guide
Assessment
This issue has not been assessed yet.