Hacker News Reader

As someone who partially uses depot but was still affected by this github issue, we obviously haven't moved over enough. We use your runners but github is still blocking us.

Hope you don't mind the public ask, it seems useful for others.

If we're using depot runners, and want to use them directly, or move off of github actions being the controller for when things run: what do you suggest?

Trigger the workflows directly on depot via CLI?

View on HN

Yes, triggering Depot CI via the CLI is the sure fire way to avoid all dependencies on GitHub.

We’d need more details around what you’re seeing. It is true that if auth across GitHub is broken than we can’t copy your actions out to be used by Depot CI. However, we have a solution in the works for that as well.

In short, Depot CI, our own engine and control plane is not dependent on upstream actions control plane. But still has to listen for commit events to know if/when to run jobs on things like PRs. This to is being removed in the future.

Reply on news.ycombinator.com