Compare commits

...

5 Commits

Author SHA1 Message Date
Nelson Wolf 73644d9d5e
Merge 67fd9409c7 into 9e436ba9f2 2025-09-29 10:47:44 +00:00
CrazyMax 9e436ba9f2
Merge pull request #1413 from osman-butt/docs/update-checkout-v5
docs: update checkout action to v5 in README examples
2025-09-29 12:15:59 +02:00
osman-butt 62929198b5 docs: update checkout action to v5 in README
Signed-off-by: osman-butt <butt.osman@gmail.com>
2025-09-06 00:04:00 +02: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 8 additions and 7 deletions

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, including processing of the `.dockerignore` file** 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
@ -131,7 +132,7 @@ jobs:
steps:
-
name: Checkout
uses: actions/checkout@v4
uses: actions/checkout@v5
-
name: Login to Docker Hub
uses: docker/login-action@v3