Quick Reference
Quick Reference
This section gives you the essentials in a format you can quickly scan when you need a reminder.
Daily Workflow Checklist
Starting new work:
- Pull latest master
- Create branch:
{type}/{description}or{type}/{feature-id}-{description} - Create draft PR (include card ID in title if using Superthread)
During work:
- Merge master into your branch at the start of each day
- Commit logical chunks of work
- Push changes regularly
- Strive to commit your work by end of day
Finishing work:
- Mark PR ready:
gh pr ready - Self-review the diff
- Merge:
gh pr merge --squash - Delete branch
Essential Commands
Copy and paste these when you need them:
# Starting work
git checkout master && git pull
git checkout -b feat/add-feature
git commit --allow-empty -m "feat: start feature work"
git push -u origin feat/add-feature
gh pr create --draft --title "feat: Add feature ST-XXX"
# During work (start of day)
git checkout master && git pull
git checkout feat/add-feature
git merge master
# During work (making changes)
git add .
git commit -m "feat: descriptive message"
git push
# Finishing work
gh pr ready
gh pr merge --squash
git checkout master && git pull
git branch -d feat/add-feature
Branch Naming Examples
Real scenarios and how to name the branch:
| What You're Doing | Branch Name |
|---|---|
| Add user authentication | feat/add-user-auth |
| Feature epic work | feat/FT050-workflow-automation |
| Fix extension popup | fix/firefox-popup |
| Update documentation | docs/workflow-guide |
| Refactor API client | refactor/api-client |
| Update dependencies | chore/update-deps |
| Add missing tests | test/link-validation |
Commit Message Examples
Real scenarios and how to write the commit message:
| What You're Doing | Commit Message |
|---|---|
| Add new feature | feat: add link archival endpoint |
| Fix a bug | fix: resolve popup sizing on Firefox |
| Update docs | docs: add Superthread integration guide |
| Refactor code | refactor: extract link validation to service |
| Update deps | chore: update Ruby to 3.4.2 |
| Add tests | test: add archival endpoint tests |
Conclusion
You've now got the full picture of how we work with Git and GitHub at Unio.
Conventional commits make history readable and tell a clear story of what changed.
Consistent branch naming enables Superthread integration and helps everyone understand what work is happening.
Draft PRs provide visibility into ongoing work and enable feedback throughout development.
Squash merges keep master history clean and make it easy to understand what changed in each PR.
These patterns make the codebase easier to navigate, enable automated tooling, and help the team stay aligned. Once you get used to them, they become second nature.
Welcome to the workflow. Let's build something great.
For AI-powered assistance with common workflow tasks, check out the Cursor AI Commands page.