-
Notifications
You must be signed in to change notification settings - Fork 229
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
Adding magma linux build #897
Conversation
env: | ||
DOCKER_REGISTRY: "docker.io" | ||
DOCKER_BUILDKIT: 1 | ||
DOCKER_ID: ${{ secrets.DOCKER_ID }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these secrets properly set up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If so, aren't we pushing to conda?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think secrets are properly setup. We can certainly push to conda. What username/password do we use for pushing to Conda ? Do we have a group level user/password ? If not perhaps I can go ahead and create the user that we can store in the secrets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the only credentials are our individual account username/password currently--we already have a pytorchbot anaconda user that we can perhaps give the permissions to if @seemethere also agrees?
db913db
to
3d71e4f
Compare
Co-authored-by: Jane (Yuan) Xu <[email protected]>
No description provided.