Skipping directory .
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the GitHub Actions workflow and inspect the rsync invocation that produces “skipping directory .” in the log. Determine why the current source path is skipped and verify that the workflow synchronizes the intended contents instead.
Written by the indexing model from the issue text.
Description
+++++++++++++++++++RUNNING rsync+++++++++++++++++++
skipping directory .
+++++++++++++++++++DONE RUNNING rsync+++++++++++++++++++
I get the above on log, nothing gets synced. Any reason why ./ is skipped?
- Dominant language
- Shell
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BuildPC/rsync-with-ssh-github-actions
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
BuildPC/rsync-with-ssh-github-actions#1 · 1 comment ·
All issues in BuildPC/rsync-with-ssh-github-actions
Similar issues
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pop-os/plymouth-theme#43 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hykilpikonna/hyfetch#545 ·
-
on hold T: core-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100