-
Notifications
You must be signed in to change notification settings - Fork 61
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
migrate to github docker registry #77
Conversation
huh interesting.. didn't think I'd have the permission to push a package to your org @jcoupey , but seems it works fine. probably because it's repo-bound. are you ok with keeping |
This is the package URL: https://github.com/VROOM-Project/vroom-docker/pkgs/container/vroom-docker |
If we have a "latest" build on every master push (based on the upstream workflow that is on every PR merge), I don't really see the point of the twice a month thing. Wouldn't it be totally redundant? |
well, this master, not upstream master. it's not redundant bcs I don't push here often, usually just for releases. so the code would never get updated. I think it's fair, basically mirroring upstream to some degree. |
Right, I did not get it was about pushes to this repo. I'm fine with this setup, especially if you have some caching involved to avoid unnecessary CI stuff. |
Also:
latest
twice a month and on master pushes, making our own versioning redundantfixes #68
fixes #72