-
Notifications
You must be signed in to change notification settings - Fork 140
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
The head commit for this pull_request event is not ahead of the base commit #11
Comments
I'm also seeing this issue, a lot of failing workflows - could an option be added to drop the error to a warning? |
same issue here. |
Workaround:
|
Same here |
A reliable way to reproduce this seems to be force push event |
Same here ... |
Workaround proposed here: jitterbit/get-changed-files#11 (comment)
Workaround proposed here: jitterbit/get-changed-files#11 (comment)
* Integrate workaround for "head commit not ahead of base commit" Workaround proposed here: jitterbit/get-changed-files#11 (comment) * Vale GHA: filter out files that aren't inside docs/ directory - This helps avoid Vale running on non-content markdown files, like our typography test page. - A new select_docs_dir_files step is added. This step parses and filters the JSON added_modified output from the get_changed_files step. It then sets a new output for this filtered file list that the Vale step later reads from. - The jq command is used to filter the JSON list of files: https://stedolan.github.io/jq/ - This Stack Overflow served as inspiration: https://stackoverflow.com/questions/64482190/edit-the-value-inside-the-json-array-with-github-actions * Only run the Vale step if list of files in docs/ is not empty When the list of files was empty after the select_docs_dir_files step ran, the action would hang at the Vale step: https://github.com/linode/docs/pull/4304/checks?check_run_id=2546802169 * Vale GHA: add comments
I have cherry-picked 54f3703 (which fixes this issue) and released it in Ana06/get-changed-files@v1.2. I hope this change makes it upstream. In case it doesn't (or until it does), feel free to use Ana06/get-changed-files@v1.2 (which also supports |
When a set of commits is squashed and force pushed, it causes errors with this action. See jitterbit/get-changed-files#11
this fork fixed the issue for me |
Would love to see the fork make it into this action! |
This issue has been open for a while. We built an action similar to this one (not entirely the same) here https://github.com/younited/detect-branch-changes-action Maybe this can cover your case as well? |
Change to follow jitterbit/get-changed-files#11 and use uses: Ana06/get-changed-files@v1.2
see jitterbit/get-changed-files#11 for context when commits are pushed, then later squashed and re-pushed, the action can fail workaround is to continue on error, since the list of files changed is still correct
The previous one seems to have had a bug reported here jitterbit/get-changed-files#11
The previous one seems to have had a bug reported here jitterbit/get-changed-files#11
The previous one seems to have had a bug reported here jitterbit/get-changed-files#11
jitterbit/get-changed-files@v1 often fails with errors like: Base commit: c06f2fe Head commit: 55342d5 Error: The head commit for this pull_request event is not ahead of the base commit. Please submit an issue on this action's GitHub repo. All: components/perf-tools/msr-safe/SPECS/msr-safe.spec Added: Modified: components/perf-tools/msr-safe/SPECS/msr-safe.spec Removed: Renamed: Added or modified: components/perf-tools/msr-safe/SPECS/msr-safe.spec This issue is known since a long time but it seems the action is not maintained anymore: https://github.com/jitterbit/get-changed-files/issues?q=The+head+commit+for+this+pull_request+event+is+not+ahead https://github.com/Ana06/get-changed-files is a maintained fork that claims to have fixed this issue: jitterbit/get-changed-files#11 (comment) Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
jitterbit/get-changed-files@v1 often fails with errors like: Base commit: c06f2fe Head commit: 55342d5 Error: The head commit for this pull_request event is not ahead of the base commit. Please submit an issue on this action's GitHub repo. All: components/perf-tools/msr-safe/SPECS/msr-safe.spec Added: Modified: components/perf-tools/msr-safe/SPECS/msr-safe.spec Removed: Renamed: Added or modified: components/perf-tools/msr-safe/SPECS/msr-safe.spec This issue is known since a long time but it seems the action is not maintained anymore: https://github.com/jitterbit/get-changed-files/issues?q=The+head+commit+for+this+pull_request+event+is+not+ahead https://github.com/Ana06/get-changed-files is a maintained fork that claims to have fixed this issue: jitterbit/get-changed-files#11 (comment) Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
See jitterbit/get-changed-files#11. This action appears to be unmaintained and is superceded by Ana06/get-changed-files.
…uest event is not ahead of the base commit' Re: jitterbit/get-changed-files#11
…uest event is not ahead of the base commit' Re: jitterbit/get-changed-files#11
I squashed a bunch of commits from my PR into one, and now the action is giving me a message:
The issue is that the base commit as such no longer exists because it was squashed. However, it appears that the changed files list is still correct. Does this error need to be raised? what needs to happen to handle squashed base/head commits?
The text was updated successfully, but these errors were encountered: