First release confirmation is missleading
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 459
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
- The question is:
Please confirm that this is the first release for the current branch (default: false): yes
Could be better...
- If you say no/false, other questions are still asked before failing...
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
Locate the release command's first-release confirmation prompt and trace what happens after a false or no answer. Verify the revised wording and that the command stops without asking the remaining questions when the confirmation is declined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100