#Github Integration not working with monorepo

1 messages · Page 1 of 1 (latest)

warm mulch
#

I can't get the github integration to successfully deploy trigger from a monorepo project.
If I locally go into the packages/tasks folder in my repo and do a cli deployment, they work fine.

I have enabled the github integration and in project settings, I set the path to the trigger config file as
packages/tasks/trigger.config.ts and various other variants, but it always tells me, it can't cant find the config file..

lusty hornetBOT
#

Hi @warm mulch. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

When using the GitHub integration with a monorepo, the key is that the “Trigger config file” path must be relative to the repository root and must include the filename, not just the directory. [GitHub integration]

From your description, your monorepo matches the documented “tasks as a package” approach, where the config lives at:

packages/tasks/trigger.config.ts

In this setup:

  • The correct value for “Trigger config file” in the GitHub integration settings is exactly:

    packages/tasks/trigger.config.ts

    (no leading ./, and it must include trigger.config.ts). [GitHub integration]

If you’ve already set that and it still says it can’t find the config file, the docs don’t provide additional troubleshooting steps for this specific GitHub‑integration + monorepo resolution issue. The knowledge sources only state that the path must be relative to the repo root and include the config filename and give apps/tasks/trigger.config.ts as an example. [GitHub integration]

Since your local npx trigger.dev@latest deploy from packages/tasks works, that confirms the config itself is valid; the remaining issue is how the integration is resolving the path, which is not further documented.

Given that, the next step (per the general deployment troubleshooting guidance) is to share the details in the Trigger.dev Discord help forum so the team can look at the specific deployment logs and repo layout. [Deployment troubleshooting]

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@warm mulch Kapa.ai is still learning and improving, please let me know how I did by reacting below.

warm mulch
#

Now it works..

zealous plaza
#

Did you change anything?

warm mulch
#

I pasted the file path from kapa.ai up there, though I'm very sure it's the same.
Before that I used "copy relative path" from vscode and that was the exact same string of text.

Can I check retrospectively which path each deployment has tried to access? Would be interesting to see if there was anything wrong

olive mantle
#

Hey @warm mulch, nice that it is working now. I could look it up if you share a deployment ID of the failed builds.