From 494011d413499321bdd965d19204592694e1dd13 Mon Sep 17 00:00:00 2001 From: Mario Loriedo Date: Fri, 26 Jan 2024 22:30:32 +0100 Subject: [PATCH] Update _posts/2024-02-05-cde-customization.adoc Co-authored-by: David Kwon --- _posts/2024-02-05-cde-customization.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-02-05-cde-customization.adoc b/_posts/2024-02-05-cde-customization.adoc index d016a8d..a9de754 100644 --- a/_posts/2024-02-05-cde-customization.adoc +++ b/_posts/2024-02-05-cde-customization.adoc @@ -144,7 +144,7 @@ image::/assets/img/cde-customization/github-action.png[] {nbsp} + As a result the image will be built and pushed automatically at every commit. The https://github.com/l0rd/rails-sample/blob/dockerfile/.github/workflows/image-build.yaml#L29[branch `dockerfile` of the ruby-sample repository] pushes the image to `quay.io/mloriedo/rails-blog-cde:latest`. -NOTE: I have named the file as `.devfile.Dockerfile`: even if any name is ok I like to use the `.devfile` prefix as these images are usually used in devfiles (as we will do STEP 3). +NOTE: I have named the file as `.devfile.Dockerfile`: even though any name is ok I like to use the `.devfile` prefix as these images are usually used in devfiles (as we will do STEP 3). ### Start a new CDE using the custom image