Repository navigation
git bug bridge new: GitLab auth token format has changed (and is not accepted) #1587
Description
git bug bridge new does not accept my GitLab auth token:
-
The format has changed and does not match the regex anymore; the my local (work) GitLab instance produces tokens like:
glpat-bE8-c60h8AD4A0v-59rAr246MQj8ObF1DA.01.0y0nl1q64
(longer,.as valid character) -
Even if I update or remove the regex, the token is not accepted by
git bug bridge newshows a linter-alike error message, cp. log below.
git bug bridge new
[1]: github
[2]: gitlab
[3]: jira
[4]: launchpad-preview
target: 2
name [default]: gitlab
Gitlab server URL [https://gitlab.com/]: https://gitlab.mycompany.com/
Gitlab project URL: https://gitlab.mycompany.com/some/tools/fu
Gitlab login: myuser
You can generate a new token by visiting https://gitlab.mycompany.com/-/user_settings/personal_access_tokens.
Choose 'Create personal access token' and set the necessary access scope for your repository.
'api' access scope: to be able to make api calls
Enter token: glpat-bE8-c60h8AD4A0v-59rAr246MQj8ObF1DA.01.0y0nl1q64
Error: 87:11: illegal character U+002E '.'
Tried with git-bug v0.10.1 as well as trunk (1a5e57d, 2026-06-26) on Debian forky.
Activity
sashil450697 commentedon Aug 16, 2026
wisalia589qs commentedon Aug 16, 2026
gitlab: accept routable personal access tokens