Generic Git URL configs keep percent-encoded repo names
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- git, typescript
Research direction
Start at the generic Git connection-config compilation path and compare direct HTTP(S) URL handling with the existing file-based generic Git behavior. Reproduce the encoded-path case from the issue, then verify that name, displayName, and zoekt metadata use the decoded repository path consistently.
Written by the indexing model from the issue text.
Description
Problem
Generic Git connection configs that point directly at an HTTP(S) remote derive repo names from the raw URL pathname. If the remote path contains encoded characters, such as %20, Sourcebot stores names like github.com/test/Project%20Name instead of the decoded repo name.
Reproduction
Configure a generic Git URL such as https://github.com/test/Project%20Name%20With%20Spaces.git and compile the connection config.
Expected
The direct URL path should match the existing file-based generic Git behavior and derive github.com/test/Project Name With Spaces.
Actual
The direct URL path keeps %20 in name, displayName, and zoekt metadata.
Impact
The same remote can produce inconsistent Sourcebot/zoekt repo identifiers depending on whether it is configured as a direct URL or discovered from a local repository origin.
- Dominant language
- TypeScript
- Stars
- 3.9k
- Forks
- 374
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 39
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.
More from sourcebot-dev/sourcebot
-
bug triage needed
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
sourcebot-dev/sourcebot#1681 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
sourcebot-dev/sourcebot#1633 ·
-
ask_sb bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
sourcebot-dev/sourcebot#1137 · 4 comments ·
-
bug triage needed
Difficulty 3/5 1-2 days Newbie friendliness 48/100
sourcebot-dev/sourcebot#1661 · 1 comment ·
-
Feature
Difficulty 4/5 3-5 days Newbie friendliness 50/100
sourcebot-dev/sourcebot#1659 · 1 comment ·
All issues in sourcebot-dev/sourcebot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·