semantic-release / semantic-release/git
Issue running on local env (different branches)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Hello, can not understand that is wrong.
Have configuration in package.json
"branches": [
{ "name": "releases-v2" },
{ "name": "master", "prerelease":"alpha", "channel": "alpha" }
],
when i run in local terminal, output says that is branches different
This test run was triggered on the branch heads/releases-v2, while semantic-release is configured to only publish from releases-v2, master, therefore a new version won’t be published.
Why this is happen and that i should do to solve it?
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
Review the package.json branches configuration and the local terminal output, then reproduce the run on heads/releases-v2 to compare the detected branch with the configured names. Done means the branch-selection behavior is explained and the issue identifies the configuration or invocation change needed to make the local run behave as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100