sameersbn / sameersbn/docker-gitlab
Gitlab public projects always ask for username when cloning over http
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Same as https://gitlab.com/gitlab-org/gitlab-ce/issues/25613
This seems to be only happening for projects that existed before upgrading.
For new projects, there is no request for user/pass when one clones via http.
Same thing happens for release 8.14.2 and 8.14.4.
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
Compare the behavior of pre-upgrade and newly created projects when cloning over HTTP, using the linked GitLab issue as context. Reproduce on releases 8.14.2 and 8.14.4, then verify that public projects created before an upgrade no longer request credentials while new projects retain their current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100