# Github: Change in branch workflow

**URL:** https://discourse.flucoma.org/t/github-change-in-branch-workflow/1823
**Category:** Development and Maintenance
**Created:** [February 21, 2023, 4:53pm UTC](https://discourse.flucoma.org/t/github-change-in-branch-workflow/1823 "2023-02-21T16:53:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![weefuzzy](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/weefuzzy/32/362_2.png) [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [February 21, 2023, 4:53pm UTC](https://discourse.flucoma.org/t/github-change-in-branch-workflow/1823/1 "2023-02-21T16:53:53Z")

</div>

For anyone working with the code repos, please note that we’ve just changed from a practice of using a `dev` branch for day-to-day development, and instead just using `main` for this instead. By and large, `main` is the only branch you’ll need to interact with (unless you’re managing releases), and this should present less friction with tools.

(Releases will live on a `production` branch, FYI)