Title: How to prevent Vercel deployments when pushing a new Git branch for backup purposes?

Hello Vercel Team,

I have two Vercel projects connected to the same private GitHub repository, using the same application Root Directory.

I want to push a new, non-production Git branch solely for source-code preservation, without triggering any Vercel deployments, builds, or incremental resource usage.

Before making any changes, I would appreciate clarification on two officially documented mechanisms.

Option 1 — previewDeploymentsDisabled

1. If I enable previewDeploymentsDisabled=true on both projects before the first push of a new branch, will Vercel prevent deployment records from being created entirely?
2. If I restore the previous settings afterward, could the previously pushed commits trigger retroactive deployments, queued jobs, or resource usage?
3. Would temporarily changing this setting leave existing Production deployments, aliases, and Deployment Protection unchanged?

Option 2 — git.deploymentEnabled

4. If the first pushed commit of a new branch already contains a vercel.json with an exact branch rule set to false, does Vercel evaluate this configuration before creating any deployment record on that initial push?
5. Does this work independently for two projects connected to the same repository and application root?

Additional question

6. Is there an officially recommended, reversible way to push backup-only branches to a Git-connected repository without creating Vercel deployment activity?

I am using the Hobby plan and want to avoid any incremental charges or unintended effects on existing Production deployments.

I have not made these changes or performed a test push.

Thank you for your guidance.