7.2 Forge Limitations and Notes

• The token creation wizard is only available for github forges, because all other forges do not support using the API to create an API token. As a consequence, if the user makes a request and the necessary token cannot be found, then that results in an error. Tokens can be created at:
  • Gitlab: https://gitlab.com/profile/personal_access_tokens
  • Bitbucket: https://bitbucket.org/account/user/tarsius/app-passwords
  • Gitea: https://localhost:3000/user/settings/applications
  • Gogs: https://localhost:3000/user/settings/applications

  Also see Manually Creating and Storing a Token and How Ghub uses Auth-Source.

• As mentioned in the previous node, the variables gitea.host and gogs.host are not taken into account.
• Gitea and Gogs do not support limiting a token to certain scopes.
• The Bitbucket API is fairly broken. Some resources only work if a slash is appended while others only work if no slash is appended. I am unable to access any private repositories and some resources don’t work for me at all. Also the API is only RESTish; pagination information is part of the response body instead of the header. Due to such issues it is possible that I will eventually have to remove support for Bitbucket altogether.
• The Gitlab API documentation is not always accurate, though I don’t have an example at hand. It also isn’t structured well, making it occasionally difficult to find the information one is looking for.
• Where one would use user/repo when accessing another forge, one has to use user%2Frepo when accessing Gitlab, e.g.:

  (glab-get "/projects/python-mode-devs%2Fpython-mode")