Closed hamelsmu closed 4 years ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
Ooops I forgot that I don't actually need this! I made some changes in anticipation that this would happen and am forcing folks to build the container each time the action starts. So the action is actually no longer referencing github/repo2docker-action
Therefore I don't need any help. I guess I should stop trying to work late at night. My apologies for the noise.
@betatim @choldgraf
CORRECTION
Ooops I forgot that I don't actually need this! I made some changes in anticipation that this would happen and am forcing folks to build the container each time the action starts. So the action is actually no longer referencing
github/repo2docker-action
Therefore I don't need any help. I guess I should stop trying to work late at night. My apologies for the noise.
Part of the release process of this Action is materializing all the dependencies for this Action. Two issues:
Currently, this action is linked to github/repo2docker-action, but this should probably be in Jupyter so that Jupyter has control over it?
I would need someone (an admin) to add the secrets to this repository
DOCKER_USERNAME
andDOCKER_PASSWORD
This is the workflow in this repository
.github/workflows/docker.yaml
Can someone help me with this?