No error when cannot connect to Gitlab - No way to know what is going wrong
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Hello,
I'm trying to connect to Gitlab.
But it seems it is not working.
I entered my username, personal access token and gitlab server url (everything is right, I checked with another tool).
The account shows under the 'Remote' node but no repository appears.
To check if it may be a wrong username or token, I entered fake invalid values and I noticed Gittyup just shows no error at all...
So if Gitlab connection is not working there is absolutely no way to know why... (wrong credentials, wrong gitlab url, ... ?)
Is there at least any error log somewhere ?
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.
Research direction
Reproduce the GitLab connection with valid and invalid credentials and server URLs, then inspect how the Remote connection failure is surfaced and whether any error log is available. Done means a failed connection provides an actionable error explaining what went wrong instead of silently showing no repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100