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

Repair the release #169

Merged
merged 1 commit into from
Jan 18, 2024
Merged

Repair the release #169

merged 1 commit into from
Jan 18, 2024

Conversation

vmcj
Copy link
Member

@vmcj vmcj commented Jan 15, 2024

The repo was not properly quoted and the github.ref has another format with direct push.

@vmcj vmcj force-pushed the fix_release_gha branch 2 times, most recently from 6d7a3be to 6232213 Compare January 16, 2024 07:02
@vmcj vmcj requested a review from nickygerritsen January 16, 2024 07:08
@vmcj
Copy link
Member Author

vmcj commented Jan 18, 2024

I'll merge this as it should fix the release files already, for the PR files I'll test a bit more how to get those in the right format.

It seems that we are not allowed to push to the registry of github.actor because the actor initiates the workflow in our scope.

The repo was not properly quoted and the github.ref has another format with direct push.
The push should be done without the tag after the image.

Push resulting image to our DOMjudge GitHub container registry

Alternative is to push to the own doing the PR, but they would be able
to push another image to have the risk that in theory we test another PR
than was used in the code from the PR.

It seems to try to push the latest tag so make which tag pushed
explicit.
@vmcj vmcj merged commit 0f87362 into DOMjudge:main Jan 18, 2024
7 of 8 checks passed
@vmcj vmcj deleted the fix_release_gha branch January 18, 2024 20:50
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

Successfully merging this pull request may close these issues.

2 participants