sameersbn / sameersbn/docker-gitlab
External Issue Tracker (docker-redmine) vs hashed repositories
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hey folks!
GitLab has deprecated the "plain repositories". Now and in future the repos are in the hashed paths. Therefore I ask if it makes sense to add this info to the actual mentioned possibility https://github.com/sameersbn/docker-gitlab/blob/master/README.md#external-issue-trackers
I can create a patch which informs how to find out the hashed path to a repository. or do you think is that possible to add some magic anywhere to make that working easier again?
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 with the README's “External issue trackers” section linked in the issue and review how it describes docker-redmine integration. Document how users can find a GitLab repository's hashed path, if that is the agreed approach; otherwise clarify whether an automated solution is intended. Done means the README explains the relevant limitation and workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, shell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100