Merge pull request #119 from snowex-hackweek/update/GH-actions

Update GH actions

Author: JessicaS11

.github/actions/buildresources/action.yaml

@@ -33,7 +33,7 @@ runs:
       shell: bash -l {0}
       run: |
         ./scripts/build_resources.sh
-        
+
     - name: Dump Build Logs
       if: always()
       shell: bash -l {0}
@@ -47,10 +47,10 @@ runs:
         personal_token: ${{inputs.token}}
         publish_dir: book/_build/html
         publish_branch: gh-pages
-        cname: snowex.hackweek.io
+        cname: snowex-2022.hackweek.io
 
     - name: Save Build
-      if: ${{ always() && inputs.jb-save == 'true'}} 
+      if: ${{ always() && inputs.jb-save == 'true'}}
       uses: actions/upload-artifact@v2
       with:
         name: build

.github/workflows/test.yaml

@@ -1,10 +1,10 @@
 name: Test
 
 on:
-  schedule:
+  # schedule:
     # run this once a week (sunday midnight) to preserve cache
     # https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy
-    - cron:  '0 0 * * 0'
+    # - cron:  '0 0 * * 0'
   pull_request_target:
     types: [labeled, synchronize]
     paths:

.github/workflows/update_fr_template.yaml

@@ -14,7 +14,7 @@ parse:
     dates: "July 11-15 2022"
     github_org_url: "https://github.com/snowex-hackweek"
     book_repo: "website2022"
-    website_url: "https://snowex.hackweek.io"
+    website_url: "https://snowex-2022.hackweek.io"
     jupyterhub_url: "https://snowex.uwhackweeks.2i2c.cloud"
     slack_workspace_url: "https://snowex2022.slack.com"
     docker_image: "https://hub.docker.com/r/uwhackweek/snowex"
@@ -36,7 +36,7 @@ parse:
 execute:
   # NOTE: 'cache' to use jupyter-cache, or 'force' to run all
   execute_notebooks: 'cache'
-  exclude_patterns: 
+  exclude_patterns:
     - "**/*snowmodeling*.ipynb"
     - "**/3_common_pitfalls.ipynb"
     # Temporarily disable

book/_config.yml

@@ -9,9 +9,9 @@ parts:
     - file: logistics
     - file: COVID
     - title: Schedule
-      url: https://snowex.hackweek.io//index.html?jump_to=schedule
+      url: https://snowex-2022.hackweek.io/index.html?jump_to=schedule
     - title: Team
-      url: https://snowex.hackweek.io//index.html?jump_to=team
+      url: https://snowex-2022.hackweek.io/index.html?jump_to=team
     - file: mission
     - file: CoC
 - caption: Preparation
@@ -86,7 +86,7 @@ parts:
             - file: tutorials/microwave/swesarr/swesarr_tut
               title: SWESARR
             - file: tutorials/microwave/SoOP/SoOp_tut
-              title: Signals of Opportunity  
+              title: Signals of Opportunity
         - file: tutorials/aviris-ng/index
           title: AVIRIS-NG
           sections:

book/_toc.yml

@@ -18,7 +18,7 @@
     "* Forming Useful Queries \n",
     "* Examples \n",
     "* Exporting Data\n",
-    "* Group Excerise\n",
+    "* Group Exercise\n",
     "* QGIS Setup \n",
     "\n",
     "## Why a database?\n",
@@ -53,7 +53,7 @@
     "* Snow off DEM from USGS 3DEP at GM\n",
     "* And almost all the associated metadata\n",
     "\n",
-    "**All this and more is easily indexed, cross referencable, and put into GIS ready formats!**\n",
+    "**All this and more is easily indexed, cross referenceable, and put into GIS ready formats!**\n",
     "\n",
     "![](https://snowexsql.readthedocs.io/en/latest/_images/gallery_overview_example_12_0.png)\n",
     "\n",

book/tutorials/database/1_getting_started_example.ipynb

@@ -264,7 +264,7 @@ git push
 ```{attention}
 The below description works well for smaller files (<10 MB) or zipped archives.
 
-Your files are persisted acrosss server shutdowns and startups and you don't have
+Your files are persisted across server shutdowns and startups and you don't have
 to upload them again when you log out at the end of the day and restart anew the
 next day.
 

book/tutorials/git_and_jupyterlab/jupyter.md

@@ -54,7 +54,7 @@
    "source": [
     "## Explore Point Cloud\n",
     "In this activity, we will open a .las file, in the [plas.io free online lidar data viewer](http://plas.io/) and explore some attributes associated with a lidar data point cloud. \n",
-    "1. Load the data: under file, select Autzen stadium. To navigate around, use left click and drag to tilt up and down, righ click and drag to move around. scroll bar to zoom in and out\n",
+    "1. Load the data: under file, select Autzen stadium. To navigate around, use left click and drag to tilt up and down, right click and drag to move around. scroll bar to zoom in and out\n",
     "\n",
     "2. Adjust Intensity \n",
     "\n",