GitHub integration for project management

From job to live code, on one card.

Connect your repos, create issues from jobs and see each pull request on the job it belongs to, from review to merged, and to live when your deploys report to GitHub. Automations move the card along, and clients see the progress, never the code.

How it works

One job, from the issue to live code

Follow a job through Skybase and GitHub: the issue it starts, the branch and pull request that do the work, the review, the merge and the deployment that puts it live.

  1. 1Step 1 of 7

    Connect your repos

    An administrator installs the Skybase GitHub App, then adds the repositories a project uses with Add repository, as many as it needs. Each has its own settings: an issue label, whether new jobs become issues there, and the environments that count as live.

    A project’s GitHub settings: Add repository lists the repositories the harbour-studio account lets Skybase reach, northwind-site already connected, and Add harbour-studio/northwind-app connects the second. Its settings are open: the issue label skybase, auto-push off and production as the environment that counts as live. Below, Set up the usual flow and the GitHub accounts, with Install on another GitHub account.

  2. 2Step 2 of 7

    Create the issue from the job

    On the job's Development tab, Create issue writes the issue for you, in the repository you choose when there's more than one: the job's title and description, its due date and a link back. Already have one? Link it instead. The job's trail notes who created it.

    A job’s Development tab: Create issue, in harbour-studio/northwind-site, the first of the project’s two repositories, opens issue #142 for Sitemap and redirects. The job’s trail says Leo Ortiz created it.

  3. 3Step 3 of 7

    Copy the branch name

    Every job has a key, like SB-123. Copy branch name gives your developer sb-123-sitemap-and-redirects, and the pull request from that branch links itself to the job. So does one with the key in its title, or one that says Fixes #142.

    Copy branch name copies sb-123-sitemap-and-redirects, and pull request #148, feat: sitemap and redirects, opened by Leo Ortiz from that branch, links itself to the job as a draft with its checks running. The job’s stage moves to In progress, and the trail says Leo opened it.

  4. 4Step 4 of 7

    Review and checks

    The job shows where its pull request stands: whether its checks pass, and each review as it lands, from Changes requested to Approved. Each turn is a line in the job's trail, and a failing check puts a red Checks failing beside the stage.

    Pull request #148 is ready for review and its checks pass. Maya Chen asks for changes, then approves it, and the job’s stage moves from In review through Changes requested to Approved, each step a line in the trail.

  5. 5Step 5 of 7

    Merged

    When the pull request is merged, the job says so, with the time. If the pull request fixes the job's issue, GitHub closes the issue and the Development tab shows that too.

    Maya Chen merges pull request #148 at 11:02, and the issue it fixes, #142, closes. The job’s stage is Merged.

  6. 6Step 6 of 7

    Live

    Live needs deployments that report to GitHub. Choose which environments count as live, production unless you say otherwise, and when a deployment there succeeds with the merge in it, the job is marked Live.

    A deployment to production with the merge in it marks the job Live at 11:20, after it was merged at 11:02, and the trail says pull request #148 went live on production. Its issue, #142, is closed.

  7. 7Step 7 of 7

    The board moves itself

    Set up the usual flow and the card follows the code: In review when the pull request opens, Done when it's merged, and Live when a deployment that reports to GitHub puts it live. They're ordinary automations, so change them as you like. Hover the stage on a card and it names the pull request and its checks.

    The Northwind Rebrand board with a stage chip on each Dev card. When pull request #148 is merged, the usual flow’s rule PR merged → Done moves Sitemap and redirects from In review to Done; when a deployment to production puts it live, Deployed → Live moves it to Live. Hovering its Live stage says PR #148 · feat: sitemap and redirects · Checks passing.

The GitHub story in one Skybase window, step by step: the project’s GitHub settings, where Add repository connects a second Northwind repository; then the job Sitemap and redirects, whose Development tab creates issue #142; Copy branch name gives sb-123-sitemap-and-redirects and pull request #148 links itself; its checks pass, Maya Chen asks for changes, then approves and merges it; a production deployment marks it Live. Each step adds a line to the job’s trail, and the job’s details row shows its stage and pull request. Last, on the board, the usual flow’s rules move the card from In review to Done and then Live, and hovering its stage names the pull request.

A job's stages, in order: Not started, In progress, In review, Changes requested, Approved, Merged and Live. Without deployments that report to GitHub, Merged is the last. A failing check shows red at any stage.

Automations

Set up the usual flow in one click

In a project's GitHub settings, Set up the usual flow picks a column for each step by its name, lets you change any of them or skip one, and writes the automations below. Each watches every repository the project has, and they're ordinary rules you can edit or switch off.

  1. PR opened → In review When a pull request is opened, move to In review
  2. Changes requested → In progress When changes are requested, move to In progress, then notify the assignee
  3. PR merged → Done When a pull request is merged, move to Done
  4. Deployed → Live When a pull request goes live, move to Live

Eight GitHub triggers join the automations you already have, so a rule can start when a pull request is opened, a pull request is merged, a pull request goes live, its GitHub issue is closed, its GitHub issue is reopened, changes are requested, a pull request is approved or checks fail. Each can watch one repository or any of them. They count towards a project's 25 rules, and the usual flow skips a rule that's already there. A pull request goes live only when your deploys report to GitHub.

An automation rule named PR merged → Done, switched on: when a pull request is merged, in any repository, move to Done. It has run 6 times, and its latest run, on Sitemap and redirects, says From GitHub. Beside it, the pull request on Sitemap and redirects goes from Approved to Merged, the rule moves the job from In review to Done, and a row marked with a violet bolt and GitHub’s mark records that in the job’s activity.

Clients see progress, not code

Your client watches the job move, not the code

Guests never see the Development tab, the stage on a card, repositories, branches, or a pull request's code or title, and the job's GitHub lines stay out of their trail. A client following the project sees Sitemap and redirects move to Live, and its activity names the automation that moved it, with GitHub's mark.

  • Repositories, branches and pull requests stay with your team
  • GitHub's updates on the job reach your team only, as they happen
  • Clients read a rule's name in the activity, so name rules with them in mind

Tom Becker, the client, sees the Northwind Rebrand board: Sitemap and redirects moves from In review to Done and then to Live, with no pull requests, branches, repo names or stages on any card.

Linked accounts

Your people, your GitHub

Each person on your team links their own GitHub account from their profile, under Connected accounts. Then the job's trail and its pull requests show their name rather than their login, an issue Skybase creates is assigned to the job's assignee on GitHub, and when a review asks for changes, the pull request's author hears about it in Skybase.

  • Skybase keeps the account's username and number, never a token
  • Rules a GitHub event sets off act as the person behind it, when they're linked
  • Unlink any time from your profile. Guests can't link an account

Profile, Connected accounts: Leo Ortiz links a GitHub account and it reads Linked as @leo-ortiz, with Unlink: Skybase only reads the GitHub username, and keeps no access to the account. In the job’s trail, the line that said leo-ortiz opened pull request #148 now says Leo Ortiz opened it.

Slack

Merges and launches in your channel

Two more switches in a project's Slack settings, Pull request merged and Deployed live, post when a pull request is merged and when it goes live, with the job's key and title linking to the job, the pull request's title and the repository.

Repository names are posted, so turn them on for a channel your team uses rather than one your client is in. They show once GitHub is on for the workspace.

Two Slack messages posted by the Skybase app to the northwind-rebrand channel: Pull request #148 merged in harbour-studio/northwind-site · SB-123 Sitemap and redirects, then Live on production: #148 · SB-123 Sitemap and redirects, each with the pull request’s title and the project under it. Below, the project’s two GitHub switches, Pull request merged and Deployed live, switch on.

Built carefully

Access you can explain to your client

Skybase asks GitHub for what it needs to follow the work, and nothing that would let it change it.

A GitHub App you install

Skybase connects as a GitHub App, on the account you choose and only to the repositories you give it. Each install is checked against the GitHub account of the person installing it before it's saved.

Permissions in plain words

It reads and writes issues, and reads pull requests, checks, deployments and commit history: commit history is how it knows a merge is in a deployment. It never changes your code, and never keeps a GitHub token for a person.

Guests never see repos

Repository names, branches, pull requests and the job's GitHub lines stay with your administrators and team members: on the job, on the board and in updates as they happen.

FAQ

What people ask about GitHub

The other integrations are on the integrations page, and the rules GitHub can set off are in automations.

Who can connect GitHub?
Administrators. They turn GitHub on for the workspace in Account settings, install the Skybase GitHub App and add each project's repositories. Team members on the project see its repositories, create and link issues, copy branch names and follow pull requests. Guests can't.
Can a project use more than one repo?
Yes, as many as it needs. Create issue asks which repository when more than one has no issue for the job yet, and each repository has its own issue label and its own live environments.
How does a pull request find its job?
Put the job's key in the pull request's branch name, title or description, as Copy branch name does (sb-123-…), or close the job's issue from it with Fixes #142, Closes #142 or Resolves #142. Its repository has to be connected to the job's project.
What counts as Live?
A successful GitHub deployment to one of the repository's live environments, production unless you change it, that includes the merge. So Live needs your deploys to report to GitHub as deployments. Skybase checks the deployed commit against the merge, so an older deployment never marks it. Without deployments, Merged is the last stage.
Does the issue keep up with the job?
Yes, both ways for whether it's open. Skybase owns the issues it creates: rename the job or edit its description or due date and they follow, while an issue you linked keeps its own words. Complete or archive the job and its issues close; reopen or restore it and they reopen. When someone closes or reopens an issue on GitHub, the job shows it and your rules can act on it, but it never completes the job by itself.
Do comments sync?
No. Comments stay where they're written: GitHub's on GitHub, and Skybase's on the job.
Can clients see any of it?
Not the code. Guests never see the Development tab, the stage on a card, repository names, branches, or a pull request's code or title, and the job's GitHub lines stay out of their trail. They see the job move, and when an automation moved it, its activity names the automation, with GitHub's mark if GitHub set it off.
What can Skybase do in our GitHub account?
In the repositories you give it, it reads and writes issues, and reads pull requests, checks, deployments and commit history. It never changes your code. When someone installs it or links their account, Skybase checks with GitHub who they are, then throws the token away.
Does it work with GitHub Enterprise Server?
No. It works with repositories on github.com, public or private.
Does it cost extra?
No. GitHub is on both plans.

Link the code to the client work it's for.

Free plan, no credit card. GitHub is on every plan.

Free plan · No credit card · Clients always free