You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using this template with a username that has uppercase characters, e.g., @Raffy23, we ended up getting problems when pushing to ghcr.io using the following workflow:
This was partially addressed in keptn/gh-automation (see PRs #20, #18, #15), but it's still not a very satisfying solution as it adds complexity to keptn/gh-automation.
@christian-kreuzberger-dtx Can you please assign this to me?
Not an expert in GH actions though, I would like to help with some of your guidance. Thanks!
When using this template with a username that has uppercase characters, e.g., @Raffy23, we ended up getting problems when pushing to
ghcr.io
using the following workflow:keptn-service-template-go/.github/workflows/CI.yml
Lines 130 to 139 in d1b3d39
This was partially addressed in keptn/gh-automation (see PRs #20, #18, #15), but it's still not a very satisfying solution as it adds complexity to keptn/gh-automation.
According to docker-build-push-action Troubleshooting, a better solution would be to sanitize the repo owner directly in your workflow:
Definition of done
repository_owner
in all affected workflows in keptn-service-template-go, and use sanitized string instead ofgithub.repository_owner
Affected Workflows
The text was updated successfully, but these errors were encountered: