-
Notifications
You must be signed in to change notification settings - Fork 22
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
Info on hub.docker.com still outdated #20
Comments
Sounds like one needs to create a PR updating https://github.com/docker-library/docs/tree/master/rakudo-star This can be semi-automated via adding an |
Now that 2019.03 is on Dockerhub, why is the README still not updated? |
That'd be because nobody has made a PR to https://github.com/docker-library/docs/tree/master/rakudo-star 😄 To be clear, giving @docker-library-bot commit bits here would not do anything with The approach we take with images maintained under https://github.com/docker-library is to make the Some other images prefer to keep the documentation on Docker Hub explicitly slim and link elsewhere for documentation (either to a markdown file in GitHub or better yet to actual upstream documentation content so the documentation for the image lives within the proper upstream documentation directly). |
Let's see if I can take care of this... But I don't have the permissions
in Docker Hub, so it might be for nothing...
|
I have permission, and it's not required. But I think that an official maintainer has to make this PR. |
It doesn't require any permissions of any kind -- we just need someone to take a look at https://github.com/docker-library/docs/blob/master/rakudo-star/content.md and provide a PR to that repository updating it as desired (which we then typically ask one of the image maintainers to sign-off on whether they approve of the changes). |
Even more outdated now... |
I've updated the info that I could find how to update. If stuff's still wrong, please open a merge request against docker-library/docs. |
My comment in #15 didn't get noticed, I open a new issue.
Your repo on Docker Hub is not an automated build, you have to update the README manually.
Here you find more infos about automated builds. Seems it isn't possible to convert an existing repo, there is an open issue on Docker: docker/hub-feedback#794
I don't want to be the one who always complains, so I'll propose some changes to the README.
The text was updated successfully, but these errors were encountered: