Skip to content

Commit a8bdb87

Browse files
committed
Docker push workflow 6
1 parent 04f1c8b commit a8bdb87

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

docs/dev-notes/workflows/publish-docker-image.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@
66

77
- Builds and publishes to GitHub packages the Docker image that is used by this action.
88

9-
The action on this repo is [configured to use the Docker image](/action.yml)) that is published by this workflow.
9+
The action on this repo is [configured to use the Docker image](/action.yml) that is published by this workflow.

docs/dev-notes/workflows/test-action-workflow.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@
1313
Since this workflow executes the [Docker container action](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action) it will build and execute the docker container so if there are any issues with the action's [Dockerfile](/Dockerfile) this workflow will detect it.
1414

1515
> **Note**
16+
>
1617
> For this workflow to be able to test the action when code is pushed I created an alternate `action.yml` at `/action-local` that will build the Docker image from the repo instead of using the Docker image published in the GitHub packages (which is what the `action.yml` at the root of the repo does).
18+
>
1719
> The downside of this approach is that I need to keep both `action.yml` files, the one at the root of the repo and the one at `/action-local`, in sync.
18-
> Alternativel, I could try to setup the workflows so that this test workflow only runs after the Docker image has been published. However this approach also has problems to solve such as making sure that the checks work as expected in a pull request scenario. The current approach eliminates all problems of this type with the only downside of keeping the `action.yml` files in sync.
20+
>
21+
> Alternativel, I could try to setup the workflows so that this test workflow only runs after the Docker image has been published. However this approach also has problems to solve such as making sure that the checks work as expected in a pull request scenario. The current approach eliminates all problems of this type with the only downside of keeping the `action.yml` files in sync.

0 commit comments

Comments
 (0)