microsoft / microsoft/react-native-windows
Automatic "prerelease" -> "patch" change type in released branches
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Cherry-picking a change from master to an already released stable branch creates an error that requires beachball expertise to understand. The user-action is to replace "prerelease" with "patch" in the generated, merged file.
This use-case is likely outside of something Beachball would want internal support for, but we can add a CI step to preprocess change-files for packages where we want to apply this rule.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing CI configuration and change-file generation path for packages, then reproduce the cherry-pick from master to a released stable branch described in the issue. Confirm that the generated merged file contains the problematic change type. Done means the applicable CI preprocessing changes "prerelease" to "patch" without requiring manual Beachball expertise.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100