Getting the branch in prepare for multiple releases
- Dominant language
- JavaScript
- Stars
- 776
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
What I'm trying to achieve is setting the `next` and `latest` tags based on branches. I want ship.js to trigger a new `latest` release when on branch `main` & `next` release when on branch `next`.
**Describe the solution you'd like**
Ability to modify the publishCommand by using git branches
**Describe alternatives you've considered**
N/A.
**Additional context**
N/A.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing ship.js's publishCommand and how the current release branch or tag is selected. Compare the requested main-to-latest and next-to-next behavior, then verify that releases from each branch produce the corresponding tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100