GitRemote.extractRepositoryPath and the config parser disagree on which characters a repository slug may hold #562

New issue

claude · 2026-09-14T22:26:03Z

claude commented

2026-09-14 22:26:03 +00:00

GitRemote.extractRepositoryPath accepts characters in a repository slug that
GitLab cannot issue — #, ?, a space, % — while the .iw/config.conf
parser rejects the same characters. The two sources of the same value therefore
disagree on what a valid slug is.

Found while working IW-558 (GitLabClient.encodedRepo). The encoding defect
itself is fixed: encodedRepo now percent-encodes the slug as one path
segment, so a corrupting character can no longer break a glab api path. This
follow-up is about the input side — whether a slug that the config parser
would refuse should be able to arrive from a git remote URL at all.

Consider aligning the two: either the remote extractor applies the config
parser's character rule, or the config parser relaxes to match the extractor.
One rule, one place.

References:

core/model/Config.scala — extractRepositoryPath, repositoryOwnerAndName, config parse
IW-558 analysis: project-management/issues/IW-558/analysis.md (Hypothesis 2)

`GitRemote.extractRepositoryPath` accepts characters in a repository slug that GitLab cannot issue — `#`, `?`, a space, `%` — while the `.iw/config.conf` parser rejects the same characters. The two sources of the same value therefore disagree on what a valid slug is. Found while working IW-558 (`GitLabClient.encodedRepo`). The encoding defect itself is fixed: `encodedRepo` now percent-encodes the slug as one path segment, so a corrupting character can no longer break a `glab api` path. This follow-up is about the *input* side — whether a slug that the config parser would refuse should be able to arrive from a git remote URL at all. Consider aligning the two: either the remote extractor applies the config parser's character rule, or the config parser relaxes to match the extractor. One rule, one place. References: - `core/model/Config.scala` — `extractRepositoryPath`, `repositoryOwnerAndName`, config parse - IW-558 analysis: `project-management/issues/IW-558/analysis.md` (Hypothesis 2)

mph referenced this issue from a commit

2026-09-14 22:27:31 +00:00

workflow(IW-558): file follow-up to tracker as #562

claude referenced this issue

2026-09-14 22:27:45 +00:00

IW-558: Percent-encode the GitLab repository slug as one api path segment #563

claude added the

agent-ready

label

2026-09-14 23:05:14 +00:00

claude commented

2026-09-14 23:05:14 +00:00