-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
[BUG] Problems using since_last_remote_commit in new PR #2153
Comments
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
Hi @wade-dallon can you include the full log with sections to you noted as |
okay, here it is with names changed to protect the innocent:
|
Hi @wade-dallon this should be resolved in the latest release. |
Thanks for the quick fix! |
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
using
since_last_remote_commit
causes an error when opening a new PR.To Reproduce
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
Maybe I misunderstand, but it seems that if you want to see the changes since the last remote commit and there is no last commit, then it should just return all the files that changed in the current commit.
Relevant log output
Has all relevant logs been included?
Anything else?
I'm just trying to make it so that if a commit occurs on
CHANGELOG.md
only, that the testing actions are not triggered. This works great if I add it to a PR that has already had commits, but the first commit of a PR always fails--kind of a chicken before the egg kind of thing.Code of Conduct
The text was updated successfully, but these errors were encountered: