tag-latest: true not working about metadata-action HOT 8 CLOSED

@felipecrs https://github.com/crazy-max/ghaction-docker-meta#latest-tag

from metadata-action.

Got it. The docs says the tag-latest can be disabled if needed, but not deliberately enabled. Is that right?

Any tip on how I can achieve the same behavior as the Docker Hub Automated Build, pushing master branch to latest?

from metadata-action.

I believe the tag-latest input should be respected if provided by the user no matter what. To implement that, its default value must not be true anymore, then we treat the undefined cases.

This is very similar to an old PR I made to the legacy docker action: docker/github-actions#20

from metadata-action.

@felipecrs I think you could specify a custom tag as latest in this case with tag-custom input. Or maybe we could handle 3 states for tag-latest: auto|true|false.

from metadata-action.

@crazy-max Awesome. May I send a PR?

from metadata-action.

I experienced the same issue and am actually trying to build the master branch as latest. If you have a dedicated repository for the Docker builds, you can work around this limitation by renaming the master branch to latest 🎩

from metadata-action.

As an alternative workaround you can do what I did at felipecrs/docker-images@1900c95.

from metadata-action.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from metadata-action.