I'm deploying code to multiple orgs in **parallel** using a separately named `project-scratch-def.json` for each one. But I've come across a case where I can only deploy some triggers to one of those orgs because the triggers depend on a feature enabled in just one of the `project-scratch-def.json` files.

Ideally, for that one case, I'd like to be able to point to a separate `sfdx-project.json` in the `sfdx force:source:push` command where that file includes a second `packageDirectories` entry pointing to the triggers. Is that possible?

(An ugly way to achieve this is to use a `sfdx force:mdapi:deploy -z zipFile` command to layer MDAPI format content on top.)

<strike>Or could the triggers and their own `sfdx-project.json` just be located in separate folder in the project that the automation changes directory into and then does the `sfdx force:source:push`? Not much luck trying that so far...</strike>