New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent branch to ciBranch causing issues for --dry-run --no-ci in Github Actions #1596
Comments
hi there, @dcneiner 👋. thanks for reaching out and for the thorough investigation. it does sound like the change included in the last release would impact this behavior. i've never seen the plugin that you mention before, but i can certainly see it being useful. i do know that we've been a little bit careful about supporting unofficial behaviors, especially around these particular flags. so, i would want to get feedback from one of our other maintainers before telling you with confidence that this would be an appropriate change. this seems reasonable though, so i think starting a PR with that change is a reasonable step and we can discuss in more detail there. |
Hey @travi! Thanks for the response (and nice bumping into you here!) I was concerned about about the unofficial aspect of this request – so no worries if it isn't a good fit. I'll work on a PR with test and we can discuss there. Thank you! |
Yeah if you could start a PR, we can discuss details there. At first sight, I don't mind the change, it seems reasonable |
Thanks @gr2m and @travi for taking a look at this. I feel bad I wasted your time now that I understand the pipeline better and don't think this fix is needed. I commented on my PR #1599 before I closed it, but I think the bug I am seeing is a combination of an issue in env-ci and possibly a |
No worries, and thank you for the update :) Is there anything we should fix in https://github.com/pvdlg/env-ci/? |
@dcneiner Were you ever able to get semantic-release-github-pr running in Github Actions? I ran into a similar problem and I'm running the latest versions, so was just curious if you came to a solution. Thanks! |
Current behavior
Even when running semantic-release with
--no-ci
and--dry-run
flags, it is now switching the meaning ofbranch
toprBranch
as of version 17.1.1.My use case is using the semantic-release-github-pr adapter/plugin to post a preview of the release version and notes that will be generated if a pull request is merged. This plugin runs semantic-release with
--no-ci
and--dry-run
With version 17.1.1 it outputs this message:
Expected behavior
When the
--no-ci
flag is provided, it feels like it should not switchbranch
to useprBranch
as that is CI specific. I was thinking it might be a simple a change as this to fix (And I am happy to submit a PR, but wanted to check before opening one)index.js line in question
Version 17.1.0 works fine with the plugin/adapter.
Environment
--no-ci
and--dry-run
and acts like a pluginNote:
--branches main
is provided at run timeCI logs
The text was updated successfully, but these errors were encountered: