Git/GitHub Development Workflow

This handbook explains how we work with Git and GitHub at Unio.

If you're new to the team, this is your guide to understanding how we organize our code, track our work, and ship changes. If you've been here a while, this is the reference for our shared conventions—the patterns that keep us aligned as we build.

What You'll Learn

We'll walk through the complete development lifecycle: creating branches, writing commits, opening pull requests, and merging code. Along the way, you'll see how these practices connect to Superthread (our project management tool) and why each convention exists.

Here's what makes this workflow work:

Clear conventions help everyone understand what's happening at a glance. When branch names and commit messages follow consistent patterns, you can quickly grasp what changed and why.

Work visibility means no surprises. We use draft PRs early so the team can see what's in progress, offer feedback, and catch issues before they become problems.

Automation handles the routine stuff. Our Superthread integration automatically updates card statuses as code moves through review and merges to master.

Let's start with where all work begins: branching strategy.