Choose Your Workflow¶
Not sure which setup you need? Start here.
Which setup fits you?¶
| Situation | Workflow | Time |
|---|---|---|
| "I just want signed commits" | Single Device | 5 min |
| "I work from multiple machines" | Multi Device | 5 min with auths pair |
| "I need to sign release artifacts" | Releases | 10 min |
| "I use Radicle" | Radicle | 15 min |
Start with Single Device
If you're new to Auths, start with the Single Device workflow. You can always add more devices later -- nothing is locked in.
Decision tree¶
flowchart TD
A["Do you need to sign release artifacts?"] -->|Yes| F["Releases"]
A -->|No| B["Do you use more than one machine?"]
B -->|No| C["Single Device"]
B -->|Yes| D["Do you use Radicle?"]
D -->|No| E["Multi Device (auths pair)"]
D -->|Yes| G["Radicle"]
click C "single-device/" "Single Device Workflow"
click E "multi-device/index/" "Multi Device Workflow"
click F "releases/" "Release Signing Workflow"
click G "radicle/" "Radicle Workflow"
What each workflow covers¶
Single Device -- One identity, one machine, signed commits. The simplest path. Covers identity creation, Git config, and verification.
Multi Device -- Same identity across multiple machines. The recommended path is auths pair (QR code / short code, handles crypto automatically). For full manual control, see Manual Linking.
Releases -- Sign tarballs, binaries, and other release artifacts with auths artifact sign. Covers manual signing, CI/CD integration with GitHub Actions, and identity bundle export for stateless verification.
Radicle -- Auths identity using Radicle-compatible Git ref layouts. Covers custom layout flags and shell aliases for convenience.