semantic-release / semantic-release/git
Question about step decision
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Hello,
I am wondering why the developers decided to run the main step of pushing release commit in prepare, shouldn't this action only be run after the whole publish succeeded?
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 plugin's prepare and publish lifecycle handling in the repository, then inspect any release configuration or history that explains when the release commit is pushed. Confirm the intended ordering with the semantic-release lifecycle documentation. Done means the rationale and expected behavior are documented, or the issue is narrowed to a concrete change if the ordering is incorrect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100