Skip to content
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

Open
Spiroman opened this issue Dec 15, 2020 · 8 comments
Open

Head commit is not ahead of the base commit #19

Spiroman opened this issue Dec 15, 2020 · 8 comments

Comments

@Spiroman
Copy link

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.

@dane-stevens
Copy link

I am seeing this issue as well. The only additional info I have is that the error occurred while creating a Draft Pull-request

@dane-stevens
Copy link

Some additional info: This error occured when submitting a pull-request from a feature branch when the feature branch was behind master.

@leslitagordita
Copy link

Seeing this issue too. Any ideas on a solution?

@dane-stevens
Copy link

@leslitagordita the issue resolved after pulling the latest master changes into my feature branch.

@cristianmtr
Copy link

Is there any way to inform the user that a rebase might fix it?

@cristianmtr
Copy link

cristianmtr commented Mar 4, 2021

Would it be possible to automatically merge with master when checking files, and then get the list of changed files? We are constantly getting errors about this, when the master has had other commits in the meantime before merging the PR.

Or could you point out where in the code this could be change/added?

@royyanbach
Copy link

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

@Ana06
Copy link

Ana06 commented Jun 4, 2021

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 pull_request_target and allow to filter files using regular expressions).

Btw, this is a duplicate of #11.

matcnft added a commit to Cardano-NFTs/policyIDs that referenced this issue Nov 9, 2021
eric-wieser added a commit to leanprover-community/mathlib3 that referenced this issue Dec 14, 2022
bors bot pushed a commit to leanprover-community/mathlib3 that referenced this issue Dec 15, 2022
flyck pushed a commit to hendriknielaender/double-trouble that referenced this issue Feb 12, 2023
flyck pushed a commit to hendriknielaender/double-trouble that referenced this issue Feb 12, 2023
flyck pushed a commit to hendriknielaender/double-trouble that referenced this issue May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants