Enhanced branch support and invalid SCM access tokens
When branching features are enabled in Polaris, your projects are upgraded automatically. When upgrading a project connected to an SCM repository, Polaris retrieves the default branch name from the repository and creates the project's default branch (using the name retrieved from the repository).
Note: If the project's SCM access token is invalid, Polaris creates a default branch called
scm_token_invalid
. If this occurs, follow the steps below to create a new SCM access token and reestablish the project's SCM integration.Create a new SCM access token
scm_token_invalid
, follow these steps:-
Open your SCM service and create a token.
- Azure DevOps tokens require Read access to the Code scope.
- Bitbucket app passwords require Read permissions for Projects and Repositories.
- GitHub tokens require repo scope.
- GitLab tokens require read_repository and read_api scopes.
-
In Polaris, go to Portfolio, open an application, and open the project with the
scm_token_invalid
branch. - Go to Settings > Integrations.
- Enter your new token in the Repository Access Token field.
- Select Test your connection.
- Select Save.
-
Go to Branches and select the
scm_token_invalid
branch. - Select the repository's default branch with the SCM Branch pulldown menu and select Save.
- Repeat steps 2-9 for other projects, as required.