Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Remove user-facing error when gitauth regex does not match #8905

Closed
Assignees
Emyrk
@bpmct

Description

@bpmct

Background

Coder'sgitauth feature allows admins to link aGit Provider. When a developer goes togit clone a workspace, they can authenticate via Coder instead of having to manually manage tokens/SSH keys.

One feature of gitauth isregex matching, which allows Coder to determine what git provider to use for specificgit repositories (e.g. bitbucket.com -> provider 1, github.com -> provider 2). When there is not a valid regex match, Coder throws a pretty nasty error:

node ➜~ $ git clone https://github.com/coder/idkCloning into'idk'...ERROR: No git provider foundfor URL"https://github.com"                                                  error: unable toread askpass response from'/tmp/coder.8MaM80/coder'Usernamefor'https://github.com':

There are some cases where the user may wish to use their own authentication, such as for a personal repo (dotfiles).

Potential solutions

  1. Instead of calling out negative matches, only call out positive matches to indicate gitauth is being used
  2. Make message more passive, avoid "error" terminology.
    No matching git providers foundin Coder. Falling back to git authentication

Perhaps we could also cover this in verbose agent or server logging, to identify why a provider isn't being matched. This is a nice-to-have

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp