Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Commit

Permalink
chore: change name
Browse files Browse the repository at this point in the history
  • Loading branch information
neurosnap committed Jul 23, 2022
1 parent 84b44a0 commit 20bbec2
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 9 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# lists-publish-action
# scp-publish-action

Action to publish posts to [lists.sh](https://lists.sh)
Action to publish posts to [pico.sh](https://pico.sh) apps.

## Required params

Expand All @@ -18,7 +18,7 @@ Action to publish posts to [lists.sh](https://lists.sh)
You will need to copy your ssh private key into a secret in your github repo.
This means your key will be accessible from github. It is highly recommended
that you create a separate key specifically for github that way the private key
will only have access to your [lists.sh](https://lists.sh) account if there is a breach on github.
will only have access to your account if there is a breach on github.

### Example

Expand All @@ -38,12 +38,12 @@ jobs:
steps:
- uses: actions/checkout@master

- name: publish to lists.sh
uses: neurosnap/lists-publish-action@main
- name: publish to prose
uses: neurosnap/scp-publish-action@main
with:
user: erock
key: ${{ secrets.PRIVATE_KEY }}
src: '*.txt'
host: lists.sh
host: prose.sh
port: 2323
```
6 changes: 3 additions & 3 deletions action.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: 'lists publish action'
description: 'Action to publish posts to lists.sh'
name: 'scp publish action'
description: 'Action to publish posts to pico.sh apps'
author: 'neurosnap'
inputs:
user:
Expand All @@ -15,7 +15,7 @@ inputs:
host:
description: 'SSH address'
required: false
default: 'lists.sh'
default: 'prose.sh'
port:
description: 'SSH Port'
required: false
Expand Down

0 comments on commit 20bbec2

Please sign in to comment.