maxking / maxking/forgejo-vscode
Gitea instance hosted under subpath is not parsed correctly from HTTPS remote
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 44m
- Merged PRs (30d)
- 2
Description
Migrated from Codeberg issue #32. Originally opened by Codeberg user Apfelkern on 2026-08-27T13:59:08+02:00.
Instance URL:
https://example.org/gitea
Git remote:
https://example.org/gitea/owner/repo.git
Actual:
Could not determine owner/repo from git remote
Expected:
owner = owner
repo = repo
Workaround:
A fake preferred remote without /gitea is parsed successfully.
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
Start at the HTTPS git remote parsing and preferred-remote handling described in the issue. Reproduce with an instance under /gitea and verify that owner/repo are extracted from https://example.org/gitea/owner/repo.git while the existing workaround remains unnecessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100