1
0
Fork 0
mirror of https://github.com/shimataro/ssh-key-action.git synced 2025-06-19 22:52:10 +10:00

fix usage of rsync (#218)

This commit is contained in:
shimataro 2022-10-31 00:31:19 +09:00 committed by GitHub
parent 53a7c26e5e
commit bcb314ec07
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 3 deletions

View file

@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
## [Unreleased] ## [Unreleased]
### Fixed
* usage of `rsync` in README
### Others ### Others
* add `windows-2022`, and `macos-11` (thanks [@ViacheslavKudinov](https://github.com/ViacheslavKudinov)) * add `windows-2022`, and `macos-11` (thanks [@ViacheslavKudinov](https://github.com/ViacheslavKudinov))

View file

@ -39,8 +39,8 @@ steps:
known_hosts: ${{ secrets.KNOWN_HOSTS }} known_hosts: ${{ secrets.KNOWN_HOSTS }}
config: ${{ secrets.CONFIG }} # ssh_config; optional config: ${{ secrets.CONFIG }} # ssh_config; optional
if_key_exists: fail # replace / ignore / fail; optional (defaults to fail) if_key_exists: fail # replace / ignore / fail; optional (defaults to fail)
- name: rsync over ssh - name: rsync over SSH
run: rsync ./foo/ user@remote:bar/ run: rsync -r ./foo/ user@remote:bar/
``` ```
See [Workflow syntax for GitHub Actions](https://help.github.com/en/articles/workflow-syntax-for-github-actions) for details. See [Workflow syntax for GitHub Actions](https://help.github.com/en/articles/workflow-syntax-for-github-actions) for details.
@ -114,7 +114,7 @@ Here are some solutions:
I recommend **rsync via bastion**. I recommend **rsync via bastion**.
```bash ```bash
rsync -e "ssh bastion ssh" ./foo/ target:bar/ rsync -r -e "ssh bastion ssh" ./foo/ target:bar/
``` ```
It has some advantages over other methods: It has some advantages over other methods: