Make Github actions run on renamed develop branch (#87)

* Make Github actions run on renamed develop branch

* Update dea-intertidal-image.yml

* Automatically update integration test validation results

---------

Co-authored-by: robbibt <[email protected]>

.github/workflows/dea-intertidal-image.yml

@@ -6,7 +6,7 @@ env:
 on:
   push:
     branches:
-      - main
+      - develop
       - tests
     paths:
       - 'intertidal/**'
@@ -20,7 +20,7 @@ on:
 
   pull_request:
     branches:
-      - main
+      - develop
     paths:
       - 'intertidal/**'
       - 'data/**'
@@ -135,8 +135,8 @@ jobs:
     needs: [test]
     runs-on: ubuntu-latest
 
-    # Only run on a push to the main branch OR a release
-    if: (github.event_name == 'push' && github.ref == 'refs/heads/main') || (github.event_name == 'release')
+    # Only run on a push to the develop branch OR a release
+    if: (github.event_name == 'push' && github.ref == 'refs/heads/develop') || (github.event_name == 'release')
 
     steps:
       - name: Checkout code
@@ -161,7 +161,7 @@ jobs:
           image_name: ${{ env.IMAGE_NAME }}
           image_tag: ${{ env.RELEASE }}
 
-      - name: Get git commit hash for push to main
+      - name: Get git commit hash for unstable image name
         if: github.event_name != 'release'
         run: |
           echo "TAG=dev$(git rev-parse --short HEAD)" \

tests/README.md

@@ -10,7 +10,7 @@ Integration tests
 
 This directory contains tests that are run to verify that DEA Intertidal code runs correctly. The ``test_intertidal.py`` file runs a small-scale full workflow analysis over an intertidal flat in the Gulf of Carpentaria using the DEA Intertidal [Command Line Interface (CLI) tools](../notebooks/Intertidal_CLI.ipynb), and compares these results against a LiDAR validation DEM to produce some simple accuracy metrics.
 
-The latest integration test completed at **2024-05-07 10:13**. Compared to the previous run, it had an:
+The latest integration test completed at **2024-08-02 14:52**. Compared to the previous run, it had an:
 - RMSE accuracy of **0.14 m ( :heavy_minus_sign: no change)**
 - MAE accuracy of **0.12 m ( :heavy_minus_sign: no change)**
 - Bias of **0.12 m ( :heavy_minus_sign: no change)**

tests/validation.csv

@@ -58,3 +58,4 @@ time,Correlation,RMSE,MAE,R-squared,Bias,Regression slope
 2024-04-23 05:49:24.645404+00:00,0.975,0.141,0.121,0.95,0.116,1.11
 2024-05-06 22:50:22.431050+00:00,0.975,0.141,0.121,0.95,0.116,1.11
 2024-05-07 00:13:21.589490+00:00,0.975,0.141,0.121,0.95,0.116,1.11
+2024-08-02 04:52:31.336765+00:00,0.975,0.141,0.121,0.95,0.116,1.11