From b7c65d80da30d73caeea784961e3f92ab551e2e4 Mon Sep 17 00:00:00 2001
From: Paul Madden <136389411+maddenp-noaa@users.noreply.github.com>
Date: Wed, 31 Jan 2024 20:13:31 +0000
Subject: [PATCH] UW-493 (#404)

---
 .github/scripts/tag-check.sh                    |  9 ---------
 .github/scripts/tag-create.sh                   |  7 -------
 .github/workflows/release.yaml                  | 16 ++++++----------
 .github/workflows/test.yaml                     | 17 +++++++----------
 README.md                                       |  2 +-
 .../contributor_guide/documentation.rst         |  4 ++--
 .../contributor_guide/fork_pr_model.rst         |  2 +-
 7 files changed, 17 insertions(+), 40 deletions(-)
 delete mode 100755 .github/scripts/tag-check.sh
 delete mode 100755 .github/scripts/tag-create.sh

diff --git a/.github/scripts/tag-check.sh b/.github/scripts/tag-check.sh
deleted file mode 100755
index b79986395..000000000
--- a/.github/scripts/tag-check.sh
+++ /dev/null
@@ -1,9 +0,0 @@
-# Actions invokes script with: bash -e <script>
-
-set -ux
-f=recipe/meta.json
-tag=v$(jq -r .version $f)+$(jq -r .buildnum $f)
-if git ls-remote --tags origin | grep -q "/$tag$"; then
-  (set +x && echo TAG $tag ALREADY EXISTS)
-  exit 1
-fi
diff --git a/.github/scripts/tag-create.sh b/.github/scripts/tag-create.sh
deleted file mode 100755
index 971c9768b..000000000
--- a/.github/scripts/tag-create.sh
+++ /dev/null
@@ -1,7 +0,0 @@
-# Actions invokes script with: bash -e <script>
-
-set -ux
-f=recipe/meta.json
-tag=v$(jq -r .version $f)+$(jq -r .buildnum $f)
-git tag $tag
-git push --tags
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index 1acdc77cd..b1e01ed1b 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -2,9 +2,9 @@ name: Release
 env:
   ANACONDA_TOKEN: ${{ secrets.ANACONDA_TOKEN }}
 on:
-  push:
+  workflow_dispatch:
     branches:
-      - main
+      - '[0-9]+.[0-9]+.[0-9]+'
 jobs:
   release:
     name: Release
@@ -12,16 +12,12 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - name: Install conda
-        run:  .github/scripts/install-conda.sh
-      - name: Docs Link Check
+        run: .github/scripts/install-conda.sh
+      - name: Documentation Link Check
         run: .github/scripts/link-check.sh
       - name: Format Check
-        run:  .github/scripts/format-check.sh
+        run: .github/scripts/format-check.sh
       - name: Make Package
-        run:  .github/scripts/make-package.sh
-      - name: Check For Existing Tag
-        run:  .github/scripts/tag-check.sh
-      - name: Tag
-        run: .github/scripts/tag-create.sh
+        run: .github/scripts/make-package.sh
       - name: Publish
         run: .github/scripts/publish.sh
diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
index 2113b3b9e..cd94bd0a9 100644
--- a/.github/workflows/test.yaml
+++ b/.github/workflows/test.yaml
@@ -2,16 +2,13 @@ name: Test
 on:
   pull_request:
     branches:
-      - develop
       - main
   push:
     branches:
-      - develop
       - main
   workflow_dispatch:
     branches:
-      - develop
-      - main
+      - '**'
 jobs:
   test:
     name: Test
@@ -19,10 +16,10 @@ jobs:
     steps:
       - uses: actions/checkout@v3
       - name: Install conda
-        run:  .github/scripts/install-conda.sh
-      - name: Test
-        run:  .github/scripts/test.sh
-      - name: Format Check
-        run:  .github/scripts/format-check.sh
-      - name: Docs Link Check
+        run: .github/scripts/install-conda.sh
+      - name: Documentation Link Check
         run: .github/scripts/link-check.sh
+      - name: Format Check
+        run: .github/scripts/format-check.sh
+      - name: Test
+        run: .github/scripts/test.sh
diff --git a/README.md b/README.md
index 17e14ef57..5b74e903d 100644
--- a/README.md
+++ b/README.md
@@ -6,4 +6,4 @@ Unified Workflow Tools for use with UFS applications and beyond
 
 ## Documentation
 
-Comprehensive documentation is available for [the development version](https://uwtools.readthedocs.io/en/develop/) and for [the latest release](https://uwtools.readthedocs.io/en/main/).
+Comprehensive documentation is available for [the development version](https://uwtools.readthedocs.io/en/main/) and for [the latest release](https://uwtools.readthedocs.io/en/stable/).
diff --git a/docs/sections/contributor_guide/documentation.rst b/docs/sections/contributor_guide/documentation.rst
index 800f0b950..1a2b3bce2 100644
--- a/docs/sections/contributor_guide/documentation.rst
+++ b/docs/sections/contributor_guide/documentation.rst
@@ -24,9 +24,9 @@ If, at some point, you remove and recreate the conda development environment und
 Viewing Online Documentation
 ----------------------------
 
-Online documentation generation and hosting for ``uwtools`` is provided by :rtd:`Read the Docs<>`. The green *View Docs* button near the upper right of that page links to the official docs for the project, as built for the ``main`` branch. Docs are also generated for the ``develop`` branch and can be selected by changing **v: main** to **v: develop** via the small green pull-down menu located at the bottom of the navigation pane on the left of the page.
+Online documentation generation and hosting for ``uwtools`` is provided by :rtd:`Read the Docs<>`. The green *View Docs* button near the upper right of that page links to the official docs for the project. When viewing the documentation, the version selector at the bottom of the navigation column on the left can be used to switch between the latest development code (``main``), the latest released version (``stable``), and any previously released version.
 
-Docs are also built and published when Pull Requests (PRs) targeting the ``develop`` or ``main`` branches are opened. Visit the :rtd:`Builds page<builds>` to see recent builds, including those made for PRs. Click a PR-related build marked *Passed*, then the small *View docs* link (**not** the large green *View Docs* button) to see the docs built specifically for that PR. If your PR includes documentation updates, it may be helpful to include the URL of this build in your PR's description so that reviewers can see the rendered HTML docs and not just the modified ``.rst`` files. Note that if commits are pushed to the PR's source branch, Read the Docs will rebuild the PR docs. See the checks section near the bottom of a PR for current status, and for another link to the PR docs via the *Details* link.
+Docs are also built and temporarily published when Pull Requests (PRs) targeting the ``main`` branch are opened. Visit the :rtd:`Builds page<builds>` to see recent builds, including those made for PRs. Click a PR-related build marked *Passed*, then the small *View docs* link (**not** the large green *View Docs* button) to see the docs built specifically for that PR. If your PR includes documentation updates, it may be helpful to include the URL of this build in your PR's description so that reviewers can see the rendered HTML docs and not just the modified ``.rst`` files. Note that if commits are pushed to the PR's source branch, Read the Docs will rebuild the PR docs. See the checks section near the bottom of a PR for current status, and for another link to the PR docs via the *Details* link.
 
 Documentation Guidelines
 ------------------------
diff --git a/docs/sections/contributor_guide/fork_pr_model.rst b/docs/sections/contributor_guide/fork_pr_model.rst
index 3a3ffa400..80415e81f 100644
--- a/docs/sections/contributor_guide/fork_pr_model.rst
+++ b/docs/sections/contributor_guide/fork_pr_model.rst
@@ -19,7 +19,7 @@ Specifics for ``uwtools``
 
 When creating your PR, please follow these guidelines, specific to the ``uwtools`` project:
 
-* Ensure that your PR is targeting base repository ``ufs-community/uwtools`` and base branch ``develop``.
+* Ensure that your PR is targeting base repository ``ufs-community/uwtools`` and base branch ``main``.
 * Your PR's **Add a description** field will appear pre-populated with a template that you should complete. Provide an informative synopsis of your contribution, then mark appropriate checklist items by placing an "x" between their square brackets. You may tidy up the description by removing boilerplate text and non-selected checklist items.
 * Use the pull-down arrow on the green button below the description to initially create a :github-docs:`draft pull request<pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests>`.
 * Once your draft PR is open, visit its **Files changed** tab and add comments on any lines of code that you think reviewers will benefit from. Try to save time by proactively answering questions you suspect reviewers will ask.