Skip to main content

Git Branching Policy

The Git branching policy lets your organization set branch naming rules that apply across every application. Developers pick a branch type from a list and Koodisi applies the required prefix, so branches follow a consistent structure without anyone memorizing conventions or dropping to the command line.

Key concepts​

TermWhat it means
Organization policyA global rule set by an administrator that applies to every application in the organization
Branch typeThe category of work you are doing, such as a feature, bug, or hotfix
Branch naming patternA pattern name paired with the prefix it requires, such as Feature and feat/
Version Control panelThe panel in the application's right sidebar where you manage branches and changes

What this gives you:

  • Branches are created from a list of approved types rather than from memory.
  • Every branch across the team follows the same structure, so branches sort and filter predictably.
  • The prefix is applied by the UI before the branch is created, so a malformed name cannot reach the remote.

Setting up branch naming patterns​

Administrators define the rules for the whole organization.

Before you begin​

You need Organization Administrator permissions.

Steps​

  1. Select Settings in the left sidebar.
  2. Under Organization, select Policies.
  3. Select the Branch naming tab.
  4. Turn on the switch beside Branch Naming Patterns. Confirm at the Enable Policy prompt.
  5. Review the existing patterns. To add one, select Add custom pattern.
  6. Enter the Pattern name, such as Feature, and the Prefix it requires, such as feat/.
  7. Select the save icon.

To change a pattern, edit it in the table and save. To remove one, delete it and confirm at Delete this Policy.

How you know it worked​

Koodisi confirms with Policy added successfully or Policy updated successfully, and the pattern appears in the table. Developers creating a branch now see a Branch Type list containing your patterns, with the first one selected by default.

With no patterns defined, the table reads No policies defined.

Creating a branch that complies​

Before you begin​

  • You must be inside an application.
  • The application must be Git-enabled and connected to a remote repository.

Steps​

  1. Select the Version Control icon in the right sidebar of your application.
  2. Select the Branches tab.
  3. Select the + icon beside the Local heading.
  4. Select a Branch Type. The prefix for that type is applied for you.
  5. Enter a Branch name — a short, descriptive name for the work, such as login-page.
  6. Check Preview, which shows the final branch name with the prefix applied, such as feat/login-page.
  7. Leave Checkout branch selected, then select Create.

How you know it worked​

Koodisi confirms that the branch was created and it appears under Local. If you left Checkout branch selected, the branch name also appears at the top of the Version Control panel.

info

A new branch is based on the branch you currently have checked out. Check out and pull the intended parent branch before creating a branch from it.

When it does not work​

SymptomCauseWhat to do
The Version Control icon is missingYou are not inside an application, the application is not Git-enabled, or the selected tree node does not offer the panel.Select an application, folder, workflow, resource, or schema node in a Git-enabled application. To connect an existing application, see Add Git to an Existing Application.
The Branch Type list is missingThe policy is turned off for your organization, or no patterns are defined.Enter any valid branch name in the plain field, or ask an administrator to enable the policy under Settings > Organization > Policies.
You cannot change or remove the prefixIntentional — Koodisi enforces the prefixes your organization defined.Ask an administrator to add the pattern you need.
Invalid branch name. Please use alphanumeric characters with optional hyphens and slashes.The branch name contains unsupported characters.Use alphanumeric characters, hyphens, and slashes only.
Pattern and Prefix are requiredOne of the two fields was left empty when saving a pattern.Enter both, then save.

Frequently asked questions​

Can I turn branch naming rules off for just my application?

No. Branch naming patterns are an organization-level policy and apply to every workspace and application in the organization.

What happens if I create a branch from the command line instead?

Koodisi's UI makes the rules easy to follow but does not lock down your terminal. If you create a poorly named branch on the command line and push it, your Git provider may reject it where provider-side branch protection is also configured. Creating branches from the Branches tab is the reliable path.

Is this the same as restricting which branches can be deployed?

No. Naming patterns govern how branches are named when created. Restricting which branches can reach protected environments is a separate policy — see Protecting Deployment Branches.