-
Notifications
You must be signed in to change notification settings - Fork 60
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
Action fails when no diff between branches #56
Comments
This actually happened to me recently because I was trying to open a PR for a branch that didn't exist, and you're right, the message is a bit cryptic. Let me take a look and see if I can make it more verbose. |
okay, I have a branch for you to test! If you can reproduce the issue above, that would be great! See the description in the PR for an explanation of changes. And let me know if/when it works, and show me a screenshot / link to the action to confirm. |
You don’t have any changed commits, so there is nothing to PR. You’d want to checkout a new branch, make changes, push, then use the action. |
@DavideViolante if you get a chance, could you please review / approve the PR so that the default has this improved verbosity? |
I know... but I'd expect that the action would not fail in this case. The action executed correctly, it checked that no PR is needed, and it finishes. |
Ah I see, then I think you would want to set |
Yeah it would be a solution, but I think by default, if the PR should not be created coz there are no diff, or coz it's already opened, there should be no fail for the action. Thanks anyway, it's just my opinion, there is no right solution, it more UX perception than a bug. ps the PR is ok, better then before for sure. |
hey @DavideViolante sorry I gave you the wrong environment variable! You can set |
For this situation a new variable is needed, e.g. |
Yep would be open to a PR to add this, if desired. |
It's normal that the action fails when there are no differences between the branches?
I'd expect a fail when the action should actually open the PR, but it doesn't.
The error I get is
That is not much clear about the reason of the failure.
The text was updated successfully, but these errors were encountered: