All Collections
Reference
Setting up main branch for the project if not using master
Setting up main branch for the project if not using master

This article shows how the admin can set up the main branch name if the project is not using the usual "master" setup.

Ville Laitila avatar
Written by Ville Laitila
Updated over a week ago

It is somewhat common to use develop or something similar as the main branch name. For pull request analysis it doesn't matter, since the hook events (of GitHub, GitLab, Bitbucket, Azure DevOps and Gerrit) give complete information for Softagram about the changes (base/head SHA1). So just for the sake of automated code review, this article is not relevant.

However, if you want to keep track of the architectural changes in your main branch, and have main branch model available for Softagram Desktop usage, it is good to explicitly define main branch name for Softagram. This happens by running below command on the server (no easier way yet available):

docker exec -ti softagram python3 ui/cli/softagramservice.py setup_analysis_target --project-id PROJECT --main-branch-name develop --branch-priority-list develop,master

Remember to replace PROJECT with the UUID of your project and to replace develop with your main branch name. You may have also several, and Softagram will try them on that order one by one to find out a branch that actually exists. This way of having several might be useful in projects with multiple repositories with different branch naming conventions.
Project ID can be found out in Softagram (via browser) by looking at the URL and using the ID from the URL (bolded):

..../0b48b26d-69e4-4da1-9c2e-0e9779afa922/projects/928bae6b-b9ef-49ce-8df0-add4f75a09e5/repos
​

Did this answer your question?