The information below applies to repositories on as well as GitHub Enterprise Server, but only if you use the hub workflow features to submit for review or review change requests.

Personal access tokens

If you don't have a valid Personal Token, you may get the error message below, indicating that your token has passed its expiration date, or that it does not have the right scopes enabled






In the repository connection manager, click on the "generate" link located to the right of the input field for the personal access token.  You can find more information on how to generate a personal access token in the GitHub documentation.


Workgroup - manage hub connections



Clicking on the "generate" link brings you to the GitHub form pre-filled with most of the information needed to be provided.  Note that, in terms of permissions / scopes, Hackolade Studio only needs "repo" (aka full control of private repositories).

Workgroup - GitHub token scopes



If you don't have sufficient rights to issue tokens, you may have to request one from your administrator.


If you need to re-issue an expired token, then:

  • navigate to your list of personal access tokens on GitHub;
  • select the token that you are using for Hackolade and click the "Regenerate token" button;
  • edit the connection in Hackolade, as described above, and copy-paste the new token from GitHub.