You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7a5af36
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): keep tea's claim when a login sits below the mount
The static tea spec gave no answer when tea listed a login below the
remote's mount. With logins at a host and at a group on it, a remote
under the host's own login then went unrecognized, though main claimed
it. The spec now claims what matchForgejoLogin picks and marks the
verdict unsettled, as the managed refiner does, so it is still never
cached for a sibling remote.
CLI refiners now return the same verdict and settled flag as managed
ones. GitLab's refiner gives the same three answers in that form.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
"Install `fj` 0.6 or later from https://codeberg.org/forgejo-contrib/forgejo-cli and run `fj --host <server-url> auth add-token`, or install `tea` 0.16 or later from https://gitea.com/gitea/tea and run `tea login add` for each Forgejo or Gitea server.",
0 commit comments