find a way to block breaking changes from landing in `release-23.x`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
we had to switch release-23.x from being a semantic-release "maintenance" branch to a "release" branch (see https://github.com/openedx/paragon/pull/3345 for details)
we should find a way to ensure we don't accidentally land commits that trigger a breaking change semantic release
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 pull request #3345 and the semantic-release configuration for the release-23.x branch. Determine how to prevent commits that trigger a breaking change from landing there; done means the branch rejects or otherwise blocks such commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100