Configuration Wizard

Set Up Your Briefing

Choose your sources · configure each one · generate ready-to-commit config files.

Deploy Path

Choose whether you want to finish with manual config handoff or a browser-side GitHub deploy.

One-click with Connect GitHub

Recommended for first-time setup. Authorize GitHub first, then write files and secrets directly at Step 6.

Fine-grained PAT with contents:write, metadata:read, actions:write, and secrets:write. Add administration:write too if you want Step 6 to auto-enable Actions / workflows. Classic PAT can still use repo + workflow. Create token on GitHub → ·
GitHub is not connected yet. Connect first if you want the one-click path.
You can still complete the wizard without connecting, but you will commit files and secrets yourself.
Step 1 of 6

Pick the sources that deserve space in your morning briefing and set the reading order.

How to create a GitHub PAT

Go to GitHub → Settings → Developer settings → Personal access tokens and create a new token:

Fine-grained PAT (recommended)

  1. Token name — something descriptive, e.g. linnet-deploy
  2. Expiration — 90 days or longer recommended
  3. Resource owner — your account or org
  4. Repository access — choose Only select repositories, then pick your Linnet fork
  5. Permissions — expand Repository permissions and set:
    • Contents → Read and write
    • Metadata → Read (auto-selected, required)
    • Actions → Read and write
    • Secrets → Read and write
    • Administration → Read and write (only if you want Step 6 to auto-enable Actions / workflows)
  6. Click Generate token and copy it immediately — it is shown only once

Classic PAT (simpler, broader access)

  1. Token name — e.g. linnet-deploy
  2. Expiration — pick a duration
  3. Scopes — check repo (all sub-scopes) and workflow
  4. Click Generate token and copy immediately — shown only once