git diff

Author: ranchodeluxe

.github/workflows/pre-release.yml

@@ -53,20 +53,13 @@ jobs:
       - name: check for changes in helm-chart directory
         id: check_changes
         run: |
-          # fetch all
           git fetch --all
-
-          # get the list of files changed in the pull request compared to the last commit
-          CHANGED_FILES=$(git diff --name-only HEAD~)
-
-          # check if any files in the helm-chart/ directory have changed
-          echo "$CHANGED_FILES" | grep -q "^helm-chart/";
-          if [ $? -eq 0 ]; then
-            echo
-          "Changes detected in the helm-chart/ directory."
+          # check for changes between HEAD and previous commit in a specific directory
+          if ! git diff --quiet HEAD~ -- ./helm-chart/eoapi/; then
+            echo "Changes detected in the ./helm-chart/eoapi/ directory."
             echo "continue=true" >> $GITHUB_OUTPUT
           else
-            echo "No changes detected in the helm-chart/ directory. Exiting."
+            echo "No changes detected in the ./helm-chart/eoapi directory. Exiting."
             echo "continue=false" >> $GITHUB_OUTPUT
             exit 0
           fi

docs/release.md

@@ -7,7 +7,7 @@ All they need to do is prefix `major: `, `minor: ` or `patch: ` to the PR title
 
 2. All PRs merged against the base `main` will kick off a "pre-release" workflow that does the following:
 
-   1. detect if there are changes in the `helm-chart/` directory and if not the "pre-release.yaml" workflow exits gracefully
+   1. detect if there are changes in the `helm-chart/` directory (if no changes are detected the "pre-release.yaml" workflow exits gracefully)
 
    2. sniff the PR title to determine major, minor or patch bumps
 
@@ -17,10 +17,10 @@ All they need to do is prefix `major: `, `minor: ` or `patch: ` to the PR title
    `'release ${{ env.new_version }} for ${{ github.ref }}@${{ github.sha }}'` and body listing the new chart version
 
 
-4. The releaser should find this PR, review and merge accordingly
+3. The releaser should find this PR, review and merge accordingly
 
 
-5. Then the releaser should go to the Github release UI/UX and kick off a new release by doing the following:
+4. Then the releaser should go to the Github release UI/UX and kick off a new release by doing the following:
 
    1. click "Draft New Release"
 
@@ -32,5 +32,9 @@ All they need to do is prefix `major: `, `minor: ` or `patch: ` to the PR title
 
    5. click the "Publish release"
 
-6. This last step then kicks off another workflow called "release.yaml" which publishes the helm chart to the
+
+5. This last step then kicks off another GH Actions workflow called "release.yaml" which publishes the helm chart to the
 `gh-pages`  branch
+
+
+6. Verify the release is all good by running `helm repo update && helm search repo eoapi --versions`

helm-chart/eoapi/values.yaml

@@ -105,7 +105,6 @@ postgrescluster:
   postGISVersion: 3.4
   pgBouncerReplicas: 1
   monitoring: false
-
   instances:
   - name: eoapi
     replicas: 1