-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow passing of different Dockerfile locations #93
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
recheck |
@@ -83,6 +83,8 @@ jobs: | |||
docker-build-target: "any target" | |||
# optional: name of the docker image, default: private/<repository_name> | |||
docker-image: <your-image> | |||
# optional: path to the Dockerfile, default: ./Dockerfile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💙
@@ -74,13 +74,15 @@ on: [ push ] | |||
|
|||
jobs: | |||
gitops: | |||
uses: Staffbase/gha-workflows/.github/workflows/template_gitops.yml@v1.10.0 | |||
uses: Staffbase/gha-workflows/.github/workflows/template_gitops.yml@v1.11.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we create the release after the PR from Kai is also merged? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, if doesn't take days... 😅
Type of Change
Description
The GitOps Action actually supports passing a
docker-file
argument. However, this action doesn't support it. By adding it here, it allows us to use this action even if we have a Dockerfile that isn't in the current working directory.Checklist