Repository navigation
Comparing changes
Open a pull request
base repository: pingdotgg/t3code
base: eea9d15
head repository: pingdotgg/t3code
compare: 1ea9afa
- 9 commits
- 14 files changed
- 1 contributor
Commits on Oct 19, 2026
-
fix(server): resolve GitLab projects from authoritative URLs
Rebuilt from fixfon’s proposal in #20241; URL provenance follow-up remains unpublished.
Configuration menu - View commit details
-
Copy full SHA for 9619600 - Browse repository at this point
Copy the full SHA 9619600View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9d94d93 - Browse repository at this point
Copy the full SHA 9d94d93View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5ae3d3b - Browse repository at this point
Copy the full SHA 5ae3d3bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5764c41 - Browse repository at this point
Copy the full SHA 5764c41View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0310f0c - Browse repository at this point
Copy the full SHA 0310f0cView commit details
Commits on Nov 11, 2026
-
Merge origin/main into worktree-git-11/gitlab-project-resolution
Resolve conflicts against main's GitLab provider, PR service and MCP pull request tool changes: - Reapply GitLab project resolution as one wrapper over every provider method that takes a repository ref, including the reads and writes main added (labels, authors, references, summaries, file stats). - Keep main's GitCafe URL canonicalization and subagent `next` hints; bulk link_pull_requests records the supplied URL as provenance too. - Only resolve repository-only links on the project's own GitLab host, so links to other hosts keep being built without a host read. - watch_pull_request carries an existing link in its command, so an unlink racing the call cannot leave the watch unstarted. - Leave the checkout URL out of canonical refs: list-seeded previews stay keyed the same as direct reads, and the provider call still receives the checkout URL through requireProject. - Replace the raw glab fixture test with a provider test that covers resolution, its cache, raw selectors and a failed resolution. AI-assisted; verified with the tests and tools listed above.
Configuration menu - View commit details
-
Copy full SHA for 0ca8023 - Browse repository at this point
Copy the full SHA 0ca8023View commit details -
fix(server): repository-only GitLab links resolve through the checkou…
…t URL resolveLink read the merge request with webUrl: null, which marks a raw API selector. On a checkout under a path prefix, that read the prefixed path literally instead of resolving the project through glab. Leaving webUrl unset lets the project's own repository inherit its HTTP checkout URL, while other repositories already drop it. AI-assisted; verified with the tests and tools listed above.
Configuration menu - View commit details
-
Copy full SHA for 7f8acac - Browse repository at this point
Copy the full SHA 7f8acacView commit details -
fix(server): pull request panels read a linked GitLab MR through its URL
The detail panel asks by host, repository and number alone. On an SSH checkout of a GitLab served under a path prefix, the repository parsed from the MR URL includes the prefix, so the panel's reads went to that literal path and failed with a 404 while the watch reactor, which sends the link's URL, resolved the right project. The service now remembers the URL a read supplies for a repository and uses it for later reads of that repository that supply none. Raw selectors (null) stay raw. AI-assisted; verified with the tests and tools listed above.
Configuration menu - View commit details
-
Copy full SHA for 015c57a - Browse repository at this point
Copy the full SHA 015c57aView commit details -
fix(server): GitLab URL routing keeps raw selectors and only learns w…
…orking URLs - Repository-only link_pull_request and watch_pull_request no longer read the host first: as on main, the repository is a raw selector, and only a supplied URL becomes the link's authoritative URL. - The service learns a repository's URL only after a read through it succeeds, so a failed URL cannot displace working routing. - A learned URL is part of a read's cache identity, so a read held from the raw project is not served once the route changes. AI-assisted; verified with the tests and tools listed above.
Configuration menu - View commit details
-
Copy full SHA for 1ea9afa - Browse repository at this point
Copy the full SHA 1ea9afaView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff eea9d15...1ea9afa