From 89f28b6fc9516e05f795f3ccdc8b2bb2b6eb5449 Mon Sep 17 00:00:00 2001 From: Jared Date: Fri, 25 Sep 2020 16:09:59 -0700 Subject: [PATCH] Update actions help text. --- .github/workflows/deploy-to-iis.yml | 5 ++--- .github/workflows/deploy-via-ssh.yml | 7 +++---- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/.github/workflows/deploy-to-iis.yml b/.github/workflows/deploy-to-iis.yml index 23837adb..660b79c5 100644 --- a/.github/workflows/deploy-to-iis.yml +++ b/.github/workflows/deploy-to-iis.yml @@ -46,15 +46,14 @@ # "Deploy to IIS" action underneath "All Workflows". There should be a # banner saying "This workflow has a workflow_dispatch event trigger." # -# Click "Run workflow" and select "release". If release branch is missing, -# see below. +# Click "Run workflow" and select the branch you want to deploy. # # 5. Keeping Your Fork Updated # You'll want to keep your fork updated so you can deploy the latest # changes. There are a few ways to do it, and they're easy to find # with a little Googling. # -# Once your release branch has been updated, you can run the +# Once your branch has been updated, you can run the # workflow again manually in GitHub to re-deploy. name: Deploy To IIS diff --git a/.github/workflows/deploy-via-ssh.yml b/.github/workflows/deploy-via-ssh.yml index 9bdc5297..97cb2d40 100644 --- a/.github/workflows/deploy-via-ssh.yml +++ b/.github/workflows/deploy-via-ssh.yml @@ -25,7 +25,7 @@ # - The hostname or IP to use for the SSH connection. # - SSH_KNOWN_HOSTS # - The content to go into your known_hosts file. This should -# contain the fingerprint for the SSH host. +# contain the fingerprint for the SSH host (e.g. "{hostname} {public key}") # - SITE_URL # - The public hostname for the site (e.g. https://app.remotely.one). # This can be an IP if it's only going to be used on the local network @@ -57,15 +57,14 @@ # "Deploy via SSH" action underneath "All Workflows". There should be a # banner saying "This workflow has a workflow_dispatch event trigger." # -# Click "Run workflow" and select "release". If release branch is missing, -# see below. +# Click "Run workflow" and select the branch you want to deploy. # # 5. Keeping Your Fork Updated # You'll want to keep your fork updated so you can deploy the latest # changes. There are a few ways to do it, and they're easy to find # with a little Googling. # -# Once your release branch has been updated, you can run the +# Once your branch has been updated, you can run the # workflow again manually in GitHub to re-deploy. name: Deploy via SSH