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

add missing pipe-character for images in meta step #595

Merged
merged 1 commit into from
Jan 11, 2024

Conversation

snpz
Copy link
Contributor

@snpz snpz commented Jan 11, 2024

Hi @gaul.

As promised I had another look and I missed the pipe character in the images-definition which leads to ignored newlines which then produce the wrong outputs in the meta step.
(I tested locally in a private repo and copied my changes to the fork afterwards, i must have missed this one)

Wrong version from the failed action log including "name" from line 35 before ,enable=true:

Processing images input
  name=ghcr.io/gaul/s3proxy/container name,enable=true

How it should look

Processing images input
  name=ghcr.io/gaul/s3proxy/container,enable=true

The automatic build triggered through this PR looks correct this time, feel free to mention me if it doesn't.

Not quite sure yet, but chances are high I will try to fix those warnings too - they bother me somehow. :)

new-lines without pipe don't get treated as newlines, see https://yaml-multiline.info/
@snpz snpz marked this pull request as ready for review January 11, 2024 16:33
@gaul gaul merged commit 0af09a5 into gaul:master Jan 11, 2024
3 checks passed
@gaul
Copy link
Owner

gaul commented Jan 11, 2024

Thanks for your continued investigation of this.

@gaul
Copy link
Owner

gaul commented Jan 12, 2024

This appears to be correctly pushing again:

https://hub.docker.com/r/andrewgaul/s3proxy/tags

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