Question about step decision

Open
#536 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, javascript
Domain
release

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.

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?

Dominant language
JavaScript
Stars
339
Forks
75
Avg merge
5h 15m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/git

All issues in semantic-release/git

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.