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

Unable to use alongside github merge queues #253

Open
GeorgePen93 opened this issue Nov 1, 2024 · 0 comments
Open

Unable to use alongside github merge queues #253

GeorgePen93 opened this issue Nov 1, 2024 · 0 comments

Comments

@GeorgePen93
Copy link

We recently implemented github merge queues and this action no longer works due to how github creates a new branch for the merge queue.

We have tried to get around this issue by parsing the commit hash from the new github branch e.g. if the new merge queue branch is called gh-readonly-queue/master/pr-2541-968707c39f80422b193c65cb50938119980604c5 we parse out the 968707c39f80422b193c65cb50938119980604c5 and pass this to path-filters.

This no longer causes an error but also does not work as intended as it now no longer will recognise changes in specific files when changes have been made to them in the commit that has been parsed from the branch name.

The only thing we have noticed is this error:

Searching for merge-base master...968707c39f80422b193c65cb50938119980604c5
  /usr/bin/git show-ref master
  /usr/bin/git cat-file -e 968707c39f80422b193c65cb50938119980604c5^{commit}
  fatal: Not a valid object name 968707c39f80[42](https://github.com/org/repo-name/actions/runs/11614801720/job/32343822442#step:6:44)2b193c65cb50938119980604c5^{commit}

However the subsequent git fetch does succeed.

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

1 participant