You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a use case where we need to evaluate the next version of a build for short-lived/feature branches and during PR.
It works for feature branches when setting dry_run: true but for PR, we also need to set noCI so semantic-release could evaluate the release and not throwing an error.
It would be nice if this action could support any core options.
Regards,
The text was updated successfully, but these errors were encountered:
I forked your repo and did the implementation to add the no ci option. But now i'm having another issue when the trigger is on a PR.
Github set the branch to refs/pull/$ID/merge at checkout instead of the branch name the PR was made for. Semantic release is not able to find a releasable branch from that.
I think the core option of semantic-release should still (debug, noci, etc) be added to the action so we can workaround some use case.
I've closed this PR since adding the noci option did not work as I expected.
yea you'll get that issue with semantic release regardless of implementation or if you use this action. It's not really going to work well on a PR, even for debugging purposes
We have a use case where we need to evaluate the next version of a build for short-lived/feature branches and during PR.
It works for feature branches when setting dry_run: true but for PR, we also need to set noCI so semantic-release could evaluate the release and not throwing an error.
It would be nice if this action could support any core options.
Regards,
The text was updated successfully, but these errors were encountered: