sameersbn / sameersbn/docker-gitlab
Cloning repository via http results in empty local copy of the project.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
When I try to clone a project hosted with this gitlab using the http link, it asks for user name and password even if the repository is public. Providing the user name and pw still results in cloning an empty repository.
Message from the command line says
warning: You appear to have cloned an empty repository.
Checking connectivity... done.```
Contributor guide
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
Start by reproducing an HTTP clone of a public project hosted by this GitLab deployment and compare the result with the command-line warning shown in the issue. Investigate why authentication is requested and why the resulting local repository is empty; done means a public repository clones with its expected project contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100