Depot CI Compatibility with GitHub Actions

da7682 pts0 comments

Depot CI compatibility with GitHub Actions | Depot CI | Depot Documentation<br>For AI agents: a site index is available at /llms.txt. Append .md to any documentation, blog, changelog, or customer URL on this site to fetch its markdown source.

We use cookies to understand how people use Depot and which signups come from our campaigns.<br>Reject cookiesAccept cookies

Depot

Sign InGet started

Menu

DocumentationDocumentation<br>Clear search query

Get Started

WelcomeManage Accounts

Using Depot

ObservabilityTroubleshootingSecurityEnvironment variablesAI and agent resourcesChangelog

Depot CI

OverviewQuickstartObservability<br>Depot CI metricsDepot CI logsDepot CI test resultsGitHub checksDatadog CI VisibilityHow-To Guides<br>Manage workflow runsManage secretsConfigure OIDCBuild custom imagesDebug jobs with SSHRun steps in parallelSplit tests by timingMount a durable cache diskRetry failed stepsUse in coding agent loopsIntegrations<br>TailscaleReference<br>CompatibilityAPI ReferenceCLI Reference

Container Builds

OverviewQuickstartTroubleshootingBuild Parallelism in DepotObservability<br>Container build metricsContainer build logsHow-To Guides<br>Local DevelopmentContinuous IntegrationBuild AutoscalingDev ContainersDocker BakeDocker BuildDocker ComposeArm ContainersPrivate RegistriesOptimal Dockerfiles<br>Overview.NETGoJavaNode.jsPHPPythonRubyRustIntegrations<br>AWS CodeBuildBitbucket PipelinesBuildkiteCircleCIDepot CIFly.ioGitHub ActionsGitLab CIGoogle Cloud BuildJenkinsTailscaleTravis CI

GitHub Actions Runners

OverviewQuickstartTroubleshootingRunner TypesObservability<br>GitHub Actions metricsGitHub Actions logsGitHub Actions test resultsHow-To Guides<br>Access Private ResourcesUse Egress FilteringIntegrations<br>DependabotTailscale

Depot Cache

OverviewAuthenticationIntegrations<br>GitHub ActionsBazelGoGradleMavenmoonrepoPantssccacheTurborepo

Depot Registry

OverviewQuickstartPull-through cache

Agents

OverviewQuickstart

Depot CLI

InstallationAuthenticationReference<br>OverviewDepot CIContainer BuildsAgents

Depot API

OverviewAuthenticationDepot CI API<br>CI API ReferenceContainer Builds API<br>Container Builds SDKContainer Builds TutorialSandbox API<br>Sandbox SDK

Depot Managed

Overview and BenefitsDepot Managed on AWSUsing GPUs

Depot CI<br>Depot CI compatibility with GitHub Actions<br>Depot CI executes GitHub Actions YAML workflows. The following tables list GitHub Actions syntax, triggers, and configuration and whether they're supported in Depot CI.

Workflow-level configuration

Field Purpose Supported nameWorkflow display name✅run-nameDynamic run title✅onWorkflow triggers✅on.workflow_callReusable workflow definition✅on.workflow_call.inputsReusable workflow inputs✅permissionsToken scopes✅envWorkflow environment variables✅defaultsDefault settings (shell, working-directory)✅concurrencyConcurrency control✅jobsJobs definition✅<br>Triggers (on.*)

Field Event type Supported on.Event triggers✅on..typesEvent trigger types✅on.merge_groupMerge queue triggers✅on.push.branchesPush branch filters✅on.push.tagsPush tag filters✅on.pull_requestPull request triggers✅on.pull_request.branchesPR branch filters✅on.pull_request_targetPull request triggers from the base branch context✅on.pull_request_reviewPull request review triggers✅on.deployment_statusDeployment status triggers✅on.*.pathsPath filters✅on.scheduleCron schedule triggers✅on.workflow_call.inputs.*Reusable workflow inputs (type, default, required)✅on.workflow_call.outputsReusable workflow outputs✅on.workflow_call.secretsReusable workflow secrets definition✅on.workflow_runWorkflow run triggers✅on.workflow_dispatchManual dispatch triggers✅on.workflow_dispatch.inputsManual dispatch inputs✅on.repository_dispatchCustom events sent through the GitHub API✅on.repository_dispatch.typesCustom event type filters✅<br>Native GitHub stacked pull requests

Depot CI supports native GitHub stacked pull requests for pull_request workflows. Depot CI evaluates a stack's branches filter against its ultimate base branch, then runs the matching workflow for each pull request in the stack using that pull request's own merge ref.

For pull requests in a stack, github.event.pull_request.stack exposes the stack's number, size, position, base.ref, and base.sha. The value is null for a pull request that is not in a stack.

For ordinary pull requests without stack metadata, Depot CI continues to match pull_request.branches against the pull request's direct base branch.

Repository dispatch events

repository_dispatch lets you trigger Depot CI workflows from outside GitHub by sending a custom event to the GitHub API — useful for kicking off a run from another system (for example, a deployment provider) without polling or running your own relay.

Subscribe to every dispatch, or filter by event type with types:

" rel="nofollow" itemScope="" itemType="https://schema.org/SoftwareSourceCode">on:<br>repository_dispatch:<br>types: [deploy-succeeded]Copy code

GitHub only delivers repository_dispatch events against your repository's default branch, so the...

depot github triggers actions workflow pull

Related Articles