Branch names and squad

[mottych]

I started to use squad a little while ago, but the latest upgrade changed all ci branch names.

Is it possible to use different branch names with squad (other than dev - preview - main - insider)
I am using dev - staging - master, and feature or hotfix for transient work.
If so, how can I configure it so that when I upgfrade the workflow won't break my structure?

Also looking for: Does Squad have built-in support for automated hotfix cascading workflows (e.g., auto-merge from main → preview → dev after production bug fixes)? Or configuration options to preserve custom branch names across upgrades?

[bradygaster]

Great question! The default branch pipeline (dev -> preview -> main) is part of Squad's promotion workflow, but you're not locked into it.

The branch names are configured in .squad/config.json under the promotion settings. If you use dev -> staging -> master, you can update the config to match your flow. The key thing Squad cares about is having a pipeline — it doesn't mandate specific branch names.

For feature/hotfix branches, Squad already uses its own convention (squad/{issue-number}-{slug}) but those are transient — they get PR'd back into your main development branch. This shouldn't conflict with your existing feature/ or hotfix/ naming.

If you're seeing CI issues with the branch names, check your GitHub Actions workflow triggers — they may be hardcoded to dev/preview/main and need updating to match your branch names.