-
Notifications
You must be signed in to change notification settings - Fork 142
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
Head commit is not ahead of the base commit #19
Comments
I am seeing this issue as well. The only additional info I have is that the error occurred while creating a Draft Pull-request |
Some additional info: This error occured when submitting a pull-request from a feature branch when the feature branch was behind master. |
Seeing this issue too. Any ideas on a solution? |
@leslitagordita the issue resolved after pulling the latest master changes into my feature branch. |
Is there any way to inform the user that a rebase might fix it? |
Would it be possible to automatically merge with Or could you point out where in the code this could be change/added? |
Saw this issue on my project as well. Since it still can generate the correct files, I just let the step continue: - uses: jitterbit/get-changed-files@v1
id: get-changed-files
continue-on-error: true |
I have cherry-picked 54f3703 (which fixes this issue) and released it in Ana06/[email protected]. I hope this change makes it upstream. In case it doesn't (or until it does), feel free to use Ana06/[email protected] (which also supports Btw, this is a duplicate of #11. |
…t error (#17936) See jitterbit/get-changed-files#19 (comment) for details.
to avoid the open issue here jitterbit/get-changed-files#19
to avoid the open issue here jitterbit/get-changed-files#19
to avoid the open issue here jitterbit/get-changed-files#19
Getting the following error for some of my CI's:
The head commit for this push event is not ahead of the base commit. Please submit an issue on this action's GitHub repo.
It is getting a base commit sha which I cannot find in the git log (presumably not there at all).
This behavior is not consistent, so I couldn't give you more info.
It does still correctly identify what files were changed since the last commit.
The text was updated successfully, but these errors were encountered: