How do I connect GitHub?

Sign up for Conductor Deck, then add a GitHub step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.

Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.

What's the difference between a trigger and an action?

A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.

GitHub + Stream Deck

developer-tools · 46 triggers · 200 actions

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features Add GitHub to your Stream Deck workflows with guided setup for the connection details it needs.

Build a GitHub workflow — free See how it works

No code
Free tier
Key press or app-event trigger
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Templates featuring GitHub

Ready-made workflows that use GitHub — open one to start in seconds.

GitHub Actions Trigger

Press a Stream Deck key to request one GitHub Actions workflow run, then notify Slack to check its status

Triggers & actions

Events that start your workflow automatically.

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

New Repository Collaborator Added

Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.

Commit Event

Triggered when a new commit is pushed to a repository.

About GitHub

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

developer-tools

How to connect

Sign up for free

Create your Conductor Deck account: no credit card required.

Connect GitHub

Follow the setup prompts for GitHub. Conductor Deck handles the app authorization or required connection details inside the workflow builder.

Build a workflow

Add a GitHub action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Run it from a key, or let events fire it

Sync your workflow to a Stream Deck button, or skip the button: GitHub triggers can start it automatically when events happen.

Frequently asked questions

How do I connect GitHub?: Sign up for Conductor Deck, then add a GitHub step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
Is it free?: Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
What's the difference between a trigger and an action?: A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.