-
Notifications
You must be signed in to change notification settings - Fork 29
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 merge commit hash in the source input #262
Comments
I was looking at your last failed job in https://github.com/vivodi/docker-flexget/actions/runs/11629651174/job/32387025483#step:7:212 And doesn't seem commit
I don't think you can safely rely on merge commit as this is a reference created by GitHub to keep track of what would happen if a pull request was merged and could therefore not be part of the working tree.
Also why do you want to rely on
Did you try with?: - uses: docker/bake-action@v5
with:
source: "{{defaultContext}}" |
I want to publish Docker images generated by PRs for testing, just with running For I think it's safe to rely on merge commits as Most importantly, - uses: actions/checkout@v4
with:
ref: ${{ github.event.pull_request.merge_commit_sha }}
- uses: docker/bake-action@v5 works, but - uses: docker/bake-action@v5
with:
source: ${{ github.server_url }}/${{ github.repository }}.git#${{ github.event.pull_request.merge_commit_sha }} doesn't work, so I believe it's a bug with |
Merge commits are indeed not part of the working tree, but |
Contributing guidelines
I've found a bug, and:
Description
Unable to use merge commit hash in the source input:
This is equivalent to:
docker/bake-action@v5
cannot find the merge commit, whileactions/checkout@v4
can.This bug prevents building a Docker image based on a merge commit in a pull_request_target event.
Expected behaviour
Image is successfully built based on merge commit.
Actual behaviour
docker/bake-action@v5
cannot find the merge commit, whileactions/checkout@v4
can.Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: