microsoft / microsoft/beachball
Beachball doesn't allow empty change comments
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
We currently use Rush but are investigating options to migrate to pnpm workspaces and Lage instead. Beachball feels similar to Rush but there's one major difference: it doesn't allow supplying a blank message to the change file. This is an interesting change because that's the default behavior of Rush when you don't provide your own message. I think it would make sense to support empty messages because not all changes (especially bumping some internal dependency) deserve their own entry in the changelog.
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
Locate the change-file message validation and the tests covering change comments. Confirm how an omitted message is currently handled, then make the empty-message case valid and add coverage showing that an internal dependency change can omit its changelog entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100