Docs / Quickstart

ShipGlance is in early access. These pages describe the hosted product; sign-in opens when early access does. Join early access →

Quickstart: a live GitHub Actions deployment dashboard

ShipGlance is a hosted deployment board for teams that ship with GitHub Actions. Setup takes about two minutes. No agents, no tokens to paste, no YAML required.

What do I need to get started?

A GitHub account and at least one repository with GitHub Actions workflows. When early access opens, you sign in with GitHub — there is no password to create.

How do I connect my repositories?

1. Sign in with GitHub and name your workspace.
2. Install the GitHub App. GitHub's own install screen lets you choose all repositories or specific ones, per account or organization.
3. Done. Every connected repository with workflows appears on your board as a pipeline.

The App asks for read-only permissions. It cannot push, merge, or change anything in your repositories. If you connect more pipelines than your plan monitors, the extras show as "not monitored (plan limit)" rows — nothing disappears silently. See pricing for plan limits.

How does it know which jobs are deploys?

Your workflow's jobs become the pipeline's stages, and if a job declares a GitHub environment:, your deploy timeline is already on. A job like this is the whole setup:

jobs:
  build:
    runs-on: ubuntu-latest
  deploy:
    needs: build
    environment: production
    runs-on: ubuntu-latest

That gives you, with no configuration:

• Deploy timeline — what is deployed where, at which commit, since when.
• Drift detection — a clear badge when what is deployed no longer matches your default branch.

The board only claims what it has seen. A stage that hasn't run recently shows a neutral "not run" state, and drift reads as unknown until a deployment has actually been observed.

No environments? Mark a deploy stage by hand

If a deploy job has no environment:, it stays a plain CI stage. Open Settings and mark the stage Deploy with its environment and target. A manual choice always wins over inference, and you can reset to automatic at any time.

Prefer configuration as code? Mark stages with deploy: true in a committed file instead — see configuration.

What's next?

• Slack notifications — post deploys and failures to a channel.
• Security — what the App can and cannot see.
• Guides — walkthroughs for common setups.
• Join early access — we'll email you when sign-in opens.