semantic-release / semantic-release/git
how to pass branches configuration to npx command
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
I have been trying the below command in jenkins pipeline to set master as main release and all feature branches as pre-release with dev. (example 1.0.0-dev.1)
npx semantic-release --branches [master, {name: $branch_name , channel: dev, prerelease: dev}] --debug
unfortunately this is not formatting well when I see it in debug output hence failing the semver release.
please suggest is there any proper way to pass branches configuration from npx command.
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 Jenkins pipeline command and its debug output, focusing on how the branches configuration is passed to the npx semantic-release command. Check the repository's existing release configuration guidance or examples; done means documenting a supported command-line form that correctly handles the master and feature-branch prerelease settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100