Two-Way GitHub Sync for Apps and Repos

Overview

Connect a Taskade Genesis app to a GitHub repository and changes flow both ways. Pushes always land on a feature branch and open a pull request, so a teammate can review before merging. Pulls let you import a private repo as the starting point for a Taskade Genesis app, complete with files, structure, and history.

TL;DR: Authorize the GitHub integration, pick a repo, then push or pull. Pushes always land on a feature branch and open a pull request. Pulls work for public and private repos. Available on Pro and above. Pair with .tsk export for offline backups.

Authorize GitHub

Connect once per workspace. The integration uses your GitHub account, not a per-app token.

1. Open Settings → Integrations.
2. Click Connect next to GitHub.
3. Sign in to GitHub if prompted.
4. Pick the repos this workspace can read or write. Granting access to specific repos is safer than granting the whole organization.
5. Click Save.

You can revoke access at any time from GitHub's installed apps page or from the Integrations panel inside Taskade.

Push your app to a repo

Push when you want a teammate to review your app, run CI checks, or merge into a shared branch.

1. Open the Taskade Genesis app you want to push.
2. Click Settings → GitHub.
3. Pick the target repo from the dropdown.
4. Click Push to GitHub.

Taskade creates a feature branch named taskade/{appSlug} and opens a pull request. The PR description lists every changed file and links back to the app for context. You merge the PR in GitHub when you are ready, exactly the same as any other change.

Tip: Re-pushing the same app reuses the branch, so the PR stays open and accumulates commits until you merge.

Pull a repo into a workspace

Pull when you want to start a new Taskade Genesis app from an existing codebase, or hand a repo to a teammate who lives inside Taskade.

1. Open the workspace where the new app should live.
2. Click New → From GitHub.
3. Select a repo. Private repos appear once GitHub authorization is granted.
4. Click Import. Taskade reads the repo and creates a Taskade Genesis app preloaded with its files, components, and configuration.

The imported app is fully editable. You can keep iterating in Taskade, push changes back to the same repo, or fork it into a separate Taskade Genesis app.

What syncs

Most user-visible parts of the app round-trip. Encrypted secrets and per-user state stay where they belong.

Conflict handling

When the repo and the app have diverged, Taskade does not silently overwrite either side.

The next push lands on a new branch with a suffix like taskade/{appSlug}-2. The pull request description lists the conflicting files and links to the diff. Resolve in GitHub the same way you would resolve any merge conflict, then merge the PR. The next pull from the same repo picks up the merged result.

Use the GitHub trigger to automate

Combine pushes from GitHub with Taskade automations to close the loop. The repo becomes both a source of truth and a trigger surface.

• Use the HTTP Webhook trigger and point GitHub's repo webhook at it for any event you care about.
• Use the GitHub integration's own triggers, like new PR opened or new release published, to fire automations without configuring a webhook.
• Pair either trigger with Branch and Loop to fan out across files, commits, or PR comments.

Plan availability

Two-way sync is gated to Pro and above. Free and Starter can read public repos for inspiration without sync.

See the pricing page for the latest plan matrix.

Related guides

• HTTP Webhook trigger. Pair GitHub events with custom Taskade automations.
• Project Export. Export project content as Markdown alongside the repo.
• Structured Output. Parse PR or issue payloads into typed variables.
• HTTP Request Action. Call the GitHub API directly from an automation.
• .tsk Export. Offline app kit backup that complements GitHub sync.