Why is the main branch on Github is named undefined?

Paul A Ciocan
Tera Contributor

Greetings folks,

 

I want to participate in this challenge myself to use the App Engine Studio to create an app with an external API integration.

 

As linked the app to Source Control, it created an SN branch and the supposed `main` branch was named undefined.

My question here is this common?

Either way I renamed the `undefined` branch to be `main`.

 

My other question is that, when should I create a pull request from the SN branch to the main branch?

1 ACCEPTED SOLUTION

WORKFLOW-COWBOY
ServiceNow Employee
ServiceNow Employee

What is the value of the system property "glide.source_control.git_default_branch" on your instance? This is where ServiceNow gets the value for the default branch name to be "main". 

 

Source Control typically needs to be initially set up by someone with at least the 'admin' role or source control capabilities. Can you confirm the user you are testing with has either one of these? 

 

As far as when to do a PR from a branch back to the main branch is really personal preference. When I am the only one working in a repo, I typically will just put everything in the main branch and use tags to save my spot. Just finished a cool new feature and committed to the main branch? Then create a tag with a new version number. (Ex. 1.1.0 instead of 1.0.0). 

 

Version numbers are also always going to be dictated by your organization or personal preference as well. 

 


--------------------------------------------------
Workflow Cowboy
LinkedIn: https://www.linkedin.com/in/dalestubblefield/
YouTube: https://www.youtube.com/@starlordnow

View solution in original post

1 REPLY 1

WORKFLOW-COWBOY
ServiceNow Employee
ServiceNow Employee

What is the value of the system property "glide.source_control.git_default_branch" on your instance? This is where ServiceNow gets the value for the default branch name to be "main". 

 

Source Control typically needs to be initially set up by someone with at least the 'admin' role or source control capabilities. Can you confirm the user you are testing with has either one of these? 

 

As far as when to do a PR from a branch back to the main branch is really personal preference. When I am the only one working in a repo, I typically will just put everything in the main branch and use tags to save my spot. Just finished a cool new feature and committed to the main branch? Then create a tag with a new version number. (Ex. 1.1.0 instead of 1.0.0). 

 

Version numbers are also always going to be dictated by your organization or personal preference as well. 

 


--------------------------------------------------
Workflow Cowboy
LinkedIn: https://www.linkedin.com/in/dalestubblefield/
YouTube: https://www.youtube.com/@starlordnow