-
Notifications
You must be signed in to change notification settings - Fork 13
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
Make KO_DOCKER_REPO configurable #1
Comments
With the current version if a user wants to set
or:
edit: but not this:
( That might still be confusing, since if a user forgets to set it for one step it'll revert back to It might make more sense to take an input to disable the ghcr-setting at all, so it doesn't login and doesn't set |
Thx. Instead of disabling as an option, which option do you think is most common?
I think inject as env (3) would probably be most flexible as it can be easily used elsewhere, eg to later pull this image etc by globally defining it (job vs action-level). |
Yeah I think I like not setting it if it's already set when it gets to the action. That's easy to describe and easy to implement. Thanks for the suggestion! |
It would be nice to have
KO_DOCKER_REPO
being part of the inputs, e.g.This would avoid an additional step for the user to export the variable.
The text was updated successfully, but these errors were encountered: