MetaMask / MetaMask/create-release-branch
Re-open the release spec upon error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 7
- Avg merge
- 51m
- Merged PRs (30d)
- 2
Description
When you submit a release specification that has an error, currently the tool will print the error and suggest manually re-opening the release specification to fix the error.
Instead we can automatically re-open the release specification, and include the error as a comment at the bottom of the specification for easy reference. This should make the workflow a bit smoother.
Contributor guide
No contributing guide indexed for this repository
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 tracing the command path that submits a release specification and locate the current error-handling flow that prints the error and asks for manual reopening. Done means the specification is reopened automatically and the error is added as a comment at its bottom.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100