Unable to fetch from 'origin' - ERROR: Repository not found.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by comparing Gittyup's clone and fetch behavior with the command-line SSH workflow described in the issue, including its SSH configuration and key settings. Trace the repository remote and SSH setup used by Gittyup; done means cloning and fetching the repository work through the application using the same SSH URL.
Written by the indexing model from the issue text.
Description
I created a repository at the command line yesterday and then, via Gittyup, I made my initial commit and pushed to github via SSH. Today - from a different PC - I cloned the repo, made some changes, committed to a new branch, and pushed these changes back to github.
When I got home I went back to the original PC and tried to fetch the changes, but Gittyup reported Unable to fetch from 'origin' - ERROR: Repository not found. I deleted the local copy of the repo and cloned it again, also via SSH, from the command line - this worked fine. I opened the local repo in Gittyup and it showed the new commits, but when I tried to fetch it just gave the same error.
I have tried supplying the path to my SSH config file and default SSH key file via Tools -> Options... Misc, but the error persists.
I have also double-checked that the origin remote is set correctly via Repository -> Configure Repository... -> Remotes.
If I delete my local copy of the repository and try to clone it directly from Gittyup it says: Failed to clone into <path_to_repo> - ERROR: Repository not found. I double checked that the URL field contains the correct SSH URL as copied-and-pasted from github.
Why am I unable to clone or fetch while using Gittyup when I can do so without issue from the command line? And what can I do to fix the issue, please?
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
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 Murmele/Gittyup
-
flatpak
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
macOS
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·