Synchronize
README.md
and description for your Github project to Docker Hub.
See action.yml
If your user
-name, and the repo path (slug
) are both the same on Github and Docker Hub, and README.md
is located at repo's root, it's enough to:
steps:
- uses: actions/checkout@v2
- uses: bemble/[email protected]
with:
pass: ${{ secrets.DOCKER_PASS }}
description: true
If everything needs to be specified:
steps:
- uses: actions/checkout@v2
- uses: bemble/[email protected]
with:
user: docker-username
pass: ${{ secrets.DOCKER_PASS }}
slug: organization/image-name
readme: ./docker/description.md
description: A must-have container, that you can't live without.
If your Docker Hub account uses software 2FA, you need to pass the TOTP secret:
steps:
- uses: actions/checkout@v2
- uses: bemble/[email protected]
with:
pass: ${{ secrets.DOCKER_PASS }}
totp_secret: ${{ secrets.DOCKER_TOTP_SECRET }}
description: true
The best way to get your TOTP secret is to disable 2FA and then enable 2FA. The secret is text given in step 2, "Text Code". Alternatively, your software may display it (for example, with Bitwarden, edit your entry, the secret is at the end of authentication key).
- Add your Docker Hub credentials to "Secrets" section in your repo's settings.
- Docker Hub requires
user
, andslug
to be lowercase. Conversion is done automatically for you, so that Github'suserName
becomesusername
when passed to Docker. description
sets Docker Hub short description to its literal content in all cases, except when it's set totrue
, when Github repo description is used instead. When skipped, no change is made to Docker Hub description.main
branch may sometimes be broken, or change behavior. It's highly recommended to always use tags.
The scripts and documentation in this project are released under the MIT License