Compare commits

...

3 Commits

Author SHA1 Message Date
Nelson Wolf 657735ce4a
Merge 67fd9409c7 into 88844b95d8 2025-04-10 10:17:20 +01:00
Nelson Wolf 67fd9409c7
Further .dockerignore clarification
Signed-off-by: Nelson Wolf <wolfprime@gmail.com>
2025-03-28 09:38:30 -07:00
Nelson Wolf b515073d1d
Clarify .dockerignore in README
Signed-off-by: Nelson Wolf <wolfprime@gmail.com>
2025-03-27 10:23:53 -07:00
1 changed files with 7 additions and 6 deletions

View File

@ -80,12 +80,13 @@ jobs:
tags: user/app:latest tags: user/app:latest
``` ```
Be careful because **any file mutation in the steps that precede the build step **Important Considerations for Git Context**
will be ignored, including processing of the `.dockerignore` file** since
the context is based on the Git reference. However, you can use the * **File Mutations** perfomred during your workflow will **not** be reflected in the final Docker image.
[Path context](#path-context) using the [`context` input](#inputs) alongside
the [`actions/checkout`](https://github.com/actions/checkout/) action to remove * **.dockerignore** is ignored altogether when using git context.
this restriction.
You can remove these limitations by using the [path context](#path-context) input alongside the [`actions/checkout`](https://github.com/actions/checkout/) action.
Default Git context can also be provided using the [Handlebars template](https://handlebarsjs.com/guide/) Default Git context can also be provided using the [Handlebars template](https://handlebarsjs.com/guide/)
expression `{{defaultContext}}`. Here we can use it to provide a subdirectory expression `{{defaultContext}}`. Here we can use it to provide a subdirectory