mirrors/Remotely
3
0
Fork 0
mirror of https://github.com/immense/Remotely.git synced 2025-10-26 11:27:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update actions help text.

Browse Source
This commit is contained in:
Jared 2020-09-25 16:09:59 -07:00 committed by Jared Goodwin
parent d0608b2ec8
commit 89f28b6fc9
2 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.github/workflows/deploy-to-iis.yml vendored
View File

@ -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

7
.github/workflows/deploy-via-ssh.yml vendored
View File

@ -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