Closed nshalman closed 8 months ago
@thebsdbox noticed two issues here: 1) The go code that pushes the image doesn't properly pass the error back up the stack. So it looks like the build and push succeeded in GitHub actions when it actually failed. 2) The credentials for quay are invalid and need to be updated.
This is extremely old but FYI we'll begin pushing actions into quay.io under quay.io/tinkerbell/actions/
Closing the issue as stale.
Even with both #59 and #68 having been merged, it doesn't appear that the container was pushed up to Quay. I thought the CI/CD process would have done that.
Expected Behaviour
Merges that create/update actions cause new images to be pushed to Quay.
Current Behaviour
https://quay.io/repository/tinkerbell-actions/qemuimg2disk appears empty.