From 20bbec21e36735b86b0414a8789d6ae5e40588cd Mon Sep 17 00:00:00 2001
From: Eric Bower <me@erock.io>
Date: Fri, 22 Jul 2022 23:47:07 -0400
Subject: [PATCH] chore: change name

---
 README.md  | 12 ++++++------
 action.yml |  6 +++---
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index ceb3fb5..e64e289 100644
--- a/README.md
+++ b/README.md
@@ -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
 
@@ -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
 
@@ -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 
 ```
diff --git a/action.yml b/action.yml
index df25489..7245bc8 100644
--- a/action.yml
+++ b/action.yml
@@ -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:
@@ -15,7 +15,7 @@ inputs:
   host:
     description: 'SSH address'
     required: false
-    default: 'lists.sh'
+    default: 'prose.sh'
   port:
     description: 'SSH Port'
     required: false