Further .dockerignore clarification

Signed-off-by: Nelson Wolf <wolfprime@gmail.com>
This commit is contained in:
Nelson Wolf 2025-03-28 09:38:30 -07:00 committed by GitHub
parent b515073d1d
commit 67fd9409c7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -80,12 +80,13 @@ jobs:
tags: user/app:latest
```
Be careful because **any file mutation in the steps that precede the build step
will be ignored. Additionally the `.dockerignore` file is not used and can only be utilized by using path context.** since
the context is based on the Git reference. However, you can use the
[Path context](#path-context) using the [`context` input](#inputs) alongside
the [`actions/checkout`](https://github.com/actions/checkout/) action to remove
this restriction.
**Important Considerations for Git Context**
* **File Mutations** perfomred during your workflow will **not** be reflected in the final Docker image.
* **.dockerignore** is ignored altogether when using git context.
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/)
expression `{{defaultContext}}`. Here we can use it to provide a subdirectory