From 5d811fd34f2a1eeda8fbe5bf937b50246e659f2d Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sat, 31 Dec 2022 09:34:03 +0000
Subject: [PATCH 1/4] chore(release): 3.1.0 [skip ci]
# [3.1.0](https://github.com/easingthemes/ssh-deploy/compare/v3.0.1...v3.1.0) (2022-12-31)
### Features
* add e2e tests ([40f855a](https://github.com/easingthemes/ssh-deploy/commit/40f855a08b4911c3f54b7a45306af355c6d87277))
---
docs/CHANGELOG.md | 7 +++++++
package.json | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
index 14a8b24..6f31251 100644
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@ -1,3 +1,10 @@
+# [3.1.0](https://github.com/easingthemes/ssh-deploy/compare/v3.0.1...v3.1.0) (2022-12-31)
+
+
+### Features
+
+* add e2e tests ([40f855a](https://github.com/easingthemes/ssh-deploy/commit/40f855a08b4911c3f54b7a45306af355c6d87277))
+
## [3.0.1](https://github.com/easingthemes/ssh-deploy/compare/v3.0.0...v3.0.1) (2022-10-28)
diff --git a/package.json b/package.json
index 41d082c..756b0ee 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "@draganfilipovic/ssh-deploy",
- "version": "3.0.1",
+ "version": "3.1.0",
"description": "Fast NodeJS action to deploy specific directory from `GITHUB_WORKSPACE` to a server via rsync over ssh.",
"main": "dist/index.js",
"files": [
From cde8aae19c68a2f72dd4380147ad971621c611e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dragan=20Filipovi=C4=87?= <info@frontenddot.com>
Date: Sat, 31 Dec 2022 15:11:04 +0100
Subject: [PATCH 2/4] Add stale issues Action
---
.github/workflows/stale.yml | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 .github/workflows/stale.yml
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 0000000..0a768d3
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,26 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Close stale issues
+
+on:
+ schedule:
+ - cron: '30 1 * * *'
+
+jobs:
+ stale:
+
+ runs-on: ubuntu-latest
+ permissions:
+ issues: write
+
+ steps:
+ - uses: actions/stale@v7
+ with:
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
+ stale-issue-message: 'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
+ days-before-stale: 30
+ days-before-close: 5
+ stale-issue-label: 'stale'
From 38b80f1762efd105d9275bb7bc6c2158d2443293 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dragan=20Filipovi=C4=87?= <info@frontenddot.com>
Date: Sat, 31 Dec 2022 15:13:32 +0100
Subject: [PATCH 3/4] Update README.md
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index 128e3b8..099d1f1 100644
--- a/README.md
+++ b/README.md
@@ -114,6 +114,8 @@ Check actions tab for example.
Check manually your ssh connection from your client before opening a bug report.
Thanks.
+More info for SSH keys: https://www.ssh.com/ssh/public-key-authentication
+
## Disclaimer
Check your keys. Check your deployment paths. And use at your own risk.
From a5d8edb94114531eec6c34662043979ac20e8201 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dragan=20Filipovi=C4=87?= <info@frontenddot.com>
Date: Sat, 31 Dec 2022 15:20:15 +0100
Subject: [PATCH 4/4] Update README.md
---
README.md | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index 099d1f1..fdc7162 100644
--- a/README.md
+++ b/README.md
@@ -107,15 +107,22 @@ jobs:
## Issues
-Almost 95% of the issues are related to wrong SSH connection.
+This is a Github Action wrapping `rsync` via `ssh`. Only issues with action functionality can be fixed here.
+
+Almost 95% of the issues are related to wrong SSH connection or `rsync` params and permissions.
+This issues are not related to the action itself.
+
+- Check manually your ssh connection from your client before opening a bug report.
+- Check `rsync` params for your usecase. Default params are not going to be enough wor everyone, it highly depends on your setup.
+- Check manually your rsync command from your client before opening a bug report.
+
I've added e2e test for this action.
+Real example is executed on every PR merge to `main`.
Check actions tab for example.
-Check manually your ssh connection from your client before opening a bug report.
-Thanks.
-
More info for SSH keys: https://www.ssh.com/ssh/public-key-authentication
+
## Disclaimer
Check your keys. Check your deployment paths. And use at your own risk.