Running projects
Kanban for agencies: a board your team and clients will use
How to set up a kanban board for agency work: columns for stages, statuses for states, job types, priorities and due dates that everyone can read.
9 min read
GitHub integration for project management
Client work in Skybase, code in GitHub.
Connect a repository to a project, push jobs to GitHub as issues, and see the pull requests that close them on the job. Your developers stay in GitHub; everyone else follows the work in Skybase.
Connect and push
A repository per project, an issue per job
An administrator turns GitHub on in Account settings, on the General page under Integrations, then chooses Install GitHub App in a project's GitHub settings and picks the repository, private ones included. On a job's GitHub tab, Push to GitHub creates the issue.
- The issue takes the job's title and description, its due date if it has one, and a link back to the job
- Add an Issue label to tag every issue Skybase creates
- Turn on Auto-push jobs to GitHub and each new job becomes an issue when it's created
- Each project connects to one repository, and a job has one issue
A job’s GitHub tab: the job pushed to GitHub as issue #142, which is open, and its pull request #148, merged.
Pull requests on the job
See the code on its way, without asking
When a pull request's description says Fixes #12, Closes #12 or Resolves #12, it appears on the job's GitHub tab under Pull Requests, with its number, title and branch. The person who owns the client relationship can see the work is coming.
Status on the job
Each pull request shows whether it's a draft, merged or closed, and the issue shows whether it's open or closed. GitHub tells Skybase as they change.
Archive closes the issue
Archive a job, on its own or in a bulk archive, and Skybase closes its GitHub issue. So do automations that archive finished jobs.
Each side keeps its own
Closing an issue in GitHub doesn't archive the job, and restoring a job doesn't reopen its issue. Comments stay where they're written.
Code stays with the team
Clients see the job, not the repository
Guests never see the GitHub tab, so a client following their project sees the work and its progress, not your code. Administrators and team members on the project can push jobs and follow their pull requests.
- One issue per job
- With its title, description, due date and a link back to the job.
- Fixes, Closes, Resolves
- Pull requests that name the issue appear on the job, with their status.
- No GitHub tab for guests
- Clients follow the job; the code stays with your team.
FAQ
What people ask about GitHub
The other integrations are on the integrations page, and automations can archive finished jobs for you.
Who can connect a repository?
Administrators. They turn GitHub on for the workspace, install the Skybase GitHub App, and choose one repository for each project. Administrators and team members on the project can then push its jobs to GitHub.
What goes into the issue?
The job's title and description, its due date, and a link back to the job. If the project has an issue label, the issue gets that too. Assignees, tasks, comments and files stay in Skybase.
How does a pull request get linked to a job?
Mention the issue in the pull request's description with Fixes, Closes or Resolves and its number, such as Fixes #12. The pull request then appears on the job's GitHub tab, with whether it's a draft, merged or closed.
Does archiving a job close its issue?
Yes, whether someone archives the job on its own or in bulk, or an automation archives it. Closing an issue in GitHub doesn't archive the job, and restoring a job doesn't reopen its issue.
Do comments sync between Skybase and GitHub?
No. Comments stay where they're written, and editing a job after it's pushed doesn't change the issue. What comes back from GitHub is status: whether the issue is open or closed, and the pull requests that name it.
Does it work with GitHub Enterprise Server?
No. It works with repositories on github.com, public or private, one repository per project.
Read next
Product guides
Six automations that take hand-offs off your plate
Project management automation for agencies, kept simple: six rules that assign, notify and tidy up at every hand-off, and the limits worth knowing first.
8 min read
- Guide Board, table and calendar The same jobs three ways: drag them across the board, sort and group them in the table, and plan due dates on the calendar. Read the guide
- Guide Automations Write a rule as a sentence and let the board handle hand-offs: when a job moves, changes or sits too long, assign it, move or archive it, or notify people. Read the guide
Link your next build to the client work behind it.
Free plan, no credit card. GitHub is on every plan.
Free plan · No credit card · Clients always free