From cdfaa6b723beeac2af3ac051e1d59c69427eeefc Mon Sep 17 00:00:00 2001 From: Philip Jenvey Date: Tue, 3 Feb 2026 13:23:45 -0800 Subject: [PATCH] docs(build-and-push): fix action links --- .github/workflows/docs/build-and-push.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/.github/workflows/docs/build-and-push.md b/.github/workflows/docs/build-and-push.md index fdbfaab..f9b9a93 100644 --- a/.github/workflows/docs/build-and-push.md +++ b/.github/workflows/docs/build-and-push.md @@ -3,16 +3,15 @@ This reusable GitHub Actions workflow encapsulates an end-to-end process for building and pushing a container image for a MozCloud service. -The inputs of this workflow are mostly used to configure [`docker-build`](../docker-build/README.md) -and [`docker-push`](../docker-push/README.md). See their documentation for more details on some of -these inputs. +The inputs of this workflow are mostly used to configure [`docker-build`] and [`docker-push`]. +See their documentation for more details on some of these inputs. ## Overview - Runs a `prebuild_script` to prepare the build environment (e.g. generate `version.json`) -- Builds and tags the Docker image using [`docker-build`](../docker-build/README.md) +- Builds and tags the Docker image using [`docker-build`] - Provides an optional hook to run a `postbuild_script` after building (e.g. for running tests) -- Pushes the image to GCP Artifact Registry (and optionally GitHub Container Registry) using [docker-push](../docker-push/README.md) +- Pushes the image to GCP Artifact Registry (and optionally GitHub Container Registry) using [`docker-push`] ## Inputs @@ -143,4 +142,6 @@ jobs: Is your build failing? The "[How to: Publish Container Images to GAR][how-to]" wiki page may include some answers, specifically around permissions issues. +[`docker-build`]: ../../../docker-build/README.md +[`docker-push`]: ../../../docker-push/README.md [how-to]: https://mozilla-hub.atlassian.net/wiki/spaces/SRE/pages/997163545/How+to+Publish+Container+Images+to+GAR