From 67fd9409c79d4cdd538a5898696878d69a8e631b Mon Sep 17 00:00:00 2001 From: Nelson Wolf Date: Fri, 28 Mar 2025 09:38:30 -0700 Subject: [PATCH] Further .dockerignore clarification Signed-off-by: Nelson Wolf --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 014cfdd..0acd9f3 100644 --- a/README.md +++ b/README.md @@ -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