Git Main Branch in Webinars

Ignition and Vertech have put on a few webinars about using Git. In the videos, they don’t use Master (Main) as their production code.

I have a little experience with Git and thought that the Master branch would be for production.

Does it not matter what the name is? Do you decide what the branch name is for your production environment?

Slightly off topic, but do you have links to these webinars?

1 Like

The branch names are whatever you want them to be. While a lot of developers use master or main, it can be whatever you want, there is no fixed requirements.

It all comes down if you want to try to follow a strict git methodology (like git flow) or just roll your own. It seems most Ignition workflows don’t follow exactly an existing git methodology, for our devops we only use develop and master branches and have a repo for each project, but have not yet matured to having feature or hotfix branches. Basically develop branch is always what is checked out in our DEV environment, when developer is ready they use perspective to commit the project on the gateway and push to azure. If they want to then release the project to TEST or Production, they open a Pull request that triggers deployments for the TEST environment and when the PR is closed and merged to master, the master branch is deployed to Production.

1 Like

Thank you for your response. That helps.