microsoft / microsoft/beachball
Disallow major changes by default?
Open
Nobody has claimed this yet.
breaking change
v4?
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
For a future major version of beachball, we should consider adding "major" to the default list of disallowed change types (this can always be overridden in an individual repo). In most repos of nontrivial size, major bumps should require some extra process/approval and having them available by default is often not desirable.
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
No file or test is named. Start by locating the default list of disallowed change types and its configuration tests; verify how an individual repository overrides that default. Done means major changes are disallowed by default while an explicit repository override still permits them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100