no-op to test if new PR check will skip building container images for…

… a readme update

Signed-off-by: Nick Boldt <nboldt@redhat.com>

must checkout before we can git diff, obviously

Signed-off-by: Nick Boldt <nboldt@redhat.com>

must checkout before we can git diff, obviously

Signed-off-by: Nick Boldt <nboldt@redhat.com>

.github/workflows/next-container-build.yaml

@@ -34,13 +34,21 @@ jobs:
     # check if the change for this PR necessitates a rebuild of containers
     runs-on: ubuntu-latest
     steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
       - name: check-changes
         # check changes in this commit for regex include and exclude matches; pipe to an env var
         run: |
           CHANGES="$(git diff --name-only | \
-          grep -E "/docker/|\.dockerignore|workflows/.+-container-build.yaml|Makefile|/bundle/|/config/|go.mod|go.sum|.+\.go" | \
-          grep -v -E ".+_test.go|/.rhdh/")" \
-          >> $GITHUB_ENV
+          grep -E "docker/|\.dockerignore|workflows/.+-container-build.yaml|Makefile|bundle/|config/|go.mod|go.sum|.+\.go" | \
+          grep -v -E ".+_test.go|/.rhdh/")";
+          echo "Changed files for this commit:"
+          echo "=============================="
+          echo "$CHANGES"
+          echo "=============================="
+          echo "CHANGES=$CHANGES" >> $GITHUB_ENV
 
   next-build:
     name: Next build

.github/workflows/pr-container-build.yaml

@@ -53,13 +53,23 @@ jobs:
     runs-on: ubuntu-latest
     needs: authorize
     steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: ${{ github.event.pull_request.head.ref }}
+          repository: ${{ github.event.pull_request.head.repo.full_name }}
       - name: check-changes
         # check changes in this commit for regex include and exclude matches; pipe to an env var
         run: |
           CHANGES="$(git diff --name-only | \
-          grep -E "/docker/|\.dockerignore|workflows/.+-container-build.yaml|Makefile|/bundle/|/config/|go.mod|go.sum|.+\.go" | \
-          grep -v -E ".+_test.go|/.rhdh/")" \
-          >> $GITHUB_ENV
+          grep -E "docker/|\.dockerignore|workflows/.+-container-build.yaml|Makefile|bundle/|config/|go.mod|go.sum|.+\.go" | \
+          grep -v -E ".+_test.go|/.rhdh/")";
+          echo "Changed files for this commit:"
+          echo "=============================="
+          echo "$CHANGES"
+          echo "=============================="
+          echo "CHANGES=$CHANGES" >> $GITHUB_ENV
 
   pr-build:
     name: PR Publish

README.md

@@ -5,7 +5,7 @@ The Goal of [Backstage](https://backstage.io) Operator project is creating Kuber
 The initial target is in support of Red Hat's assemblies of Backstage - specifically supporting [dynamic-plugins](https://github.com/janus-idp/backstage-showcase/blob/main/showcase-docs/dynamic-plugins.md)) on OpenShift. This includes [Janus-IDP](https://janus-idp.io/) and [Red Hat Developer Hub (RHDH)](https://developers.redhat.com/rhdh) but may be flexible enough to install any compatible Backstage instance on Kubernetes. See additional information under [Configuration](docs/configuration.md)).
 The Operator provides clear and flexible configuration options to satisfy a wide range of expectations, from "no  configuration for default quick start" to "highly customized configuration for production".
 
-[More documentation...](#more-documentation)
+[More documentation...](#more-documentation) 
 
 ## Getting Started
 You’ll need a Kubernetes or OpenShift cluster. You can use [Minikube](https://minikube.sigs.k8s.io/docs/) or [KIND](https://sigs.k8s.io/kind) for local testing, or deploy to a remote cluster.