I'm now tagging/releasing the initial version from 2022 of this workflow because there will be upcoming breaking changes as it evolves into something more flexible, with advanced use case examples.
First, you should be forking this repo, right? Which I've further highlighted in an upcoming PR for the README. I don't publish this workflow to the marketplace because it's an example and meant to be used as a repo template for making your own reusable workflows. It's not meant to be called directly, because I don't want a change on my part to break your builds.
Second, if you were to use this repo directly, it would be best to pin to this v1 release rather than main branch, so your builds don't break when I update main, like so:
uses: bretfisher/docker-build-workflow/.github/workflows/reusable-docker-build.yaml@v1