Strapi Cloud already allows configuring a Base directory for a branch (e.g. strapi/ inside a monorepo). This correctly defines where the Strapi application is located for the build, but auto-deploys are still triggered on every commit to the branch, even if no files inside the base directory were changed.

In monorepo setups (Nx, Turborepo, Yarn/pnpm workspaces), this leads to:

– Unnecessary Strapi Cloud deployments when changes only affect other apps or libraries in the repository.

– Difficulty integrating Strapi Cloud into a unified release process where CI decides which apps need to be deployed.

– The need to choose between auto-deploying on every commit, or disabling auto-deploy and having no supported way to trigger strapi deploy from CI (because the CLI requires interactive login).

Requested enhancements:

1) Path-aware auto-deploy: When a Base directory is configured, only trigger auto-deploys if commits modify files under that directory.

2) CI-friendly, non-interactive deployment: Provide a CI/service token or similar mechanism (e.g. STRAPI_CLOUD_TOKEN) so that strapi deploy can be executed from CI/CD pipelines without a browser-based login flow (like Vercel, Netlify, Amplify).

These changes would make Strapi Cloud behave predictably in monorepos, reduce redundant deployments, and allow modern CI/CD pipelines (Nx/Turborepo/other monorepo tools) to control when Strapi is actually deployed.