Overview of Branches

View and manage all branches in your Flosum project.

Written for the Old UI

This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the Where Did It Go article.

Overview

Branches in DevOps can be accessed from the Code page, which displays all available branches in the project. Each branch serves as a working copy of the codebase, allowing for independent modifications. Users can search for branches, apply filters by ownership or activity, and sort them by the latest updates.

The starting point is the main branch, which is directly synced from your Production org and serves as the single source of truth and the foundation for all development work. Developers create feature branches from the Main Branch, providing isolated workspaces while maintaining alignment with Production.

Best Practices

• Use descriptive branch names (e.g., feature/new-approval-process) to make collaboration easier.
• Regularly review Behind/Ahead counts to keep branches up to date with the main branch.
• Close or clean up stale branches to maintain a healthy repository.

Create Branch

To create a new branch, click the Create Branch button and select a source branch. For detailed instructions on creating a new branch, see the following article.

• Creating a Branch

Branches Views

The available branches can be displayed in two different views, List and Kanban, which are explained in the sections below. To switch between the views, use the view switcher.

Branches in both views can be searched and sorted.

• Search branches – quickly locate a branch by name.
• Sort by activity – reorder branches by latest updates or name.

List View (Default)

The List view displays all the branches in a table that shows key details for each branch:

Branch Value	Description
Name	The branch's name (e.g., main, ReleaseBranch).
Created By	The user who last updated the branch.
Last Activity	The time since the most recent commit, update, or activity.
Behind / Ahead	The number of commits the branch is behind or ahead of the source branch. In most cases, this will be the main branch.
Pull Requests	The linked pull requests associated with the branch.

Branch Filters

You can filter the table using the options directly above the table.

Filter	Description
All	Displays all branches.
Yours	Shows only branches you created or own.
Active	Displays branches recently updated.
Stale	Shows only branches without recent activity.

Kanban View

The Kanban view provides a visual overview of branches and their deployment locations. The board is organized by the environment to which each branch was most recently deployed. The environments correspond to the organization's environments. For example, if the feature/new-feature branch is deployed to the quality-one organization, which has a QA environment, the branch appears in the QA section of the board. The board includes the following sections.

• Not deployed yet (includes branches that have not been deployed)
• Dev
• QA
• Test
• Prod

If you are unsure which organizations are in each environment, view the Organizations table to see the environment listed for each.

Branch Card Details

Each branch is represented by a card that includes its details. The branch cards can be expanded to display more details, and each is explained in the table below.

Branch Detail	Description
Name	The branch's name (e.g., main, ReleaseBranch).
Last Activity	The time since the most recent commit, update, or activity.
Last Deployed	The time since the last deployment.
Owner	The user who created the branch.
Total Components	The number of components in the branch.
Behind / Ahead	The number of commits the branch is behind or ahead of the source branch. In most cases, this will be the main branch.
Pull Requests	The linked pull requests associated with the branch.

Selecting a Branch

To view more details about a branch and perform actions on the branch, click the branch. For comprehensive documentation on branches, see the following sections:

• Branch Actions

• Code Tools