Support a .gearsetignore file to exclude non-metadata paths from CI triggers
Salesforce DX repositories hold more than deployable metadata: AI agent guidelines, documentation, package.json, .prettierrc, lint configs, scripts and so on. A push that only touches these files still starts a CI job. The job deploys or validates zero components, and on a production pipeline it can still run the full test suite, which can take an hour or more.
Gearset has no way to exclude paths from this. .gitignore isn’t a fix because it stops the files from being tracked at all, and we need them in version control.
Proposal
A .gearsetignore file in the repository root, with the same syntax as .gitignore (glob patterns, negation, directory paths).
- A push that changes only ignored paths doesn’t trigger a CI job.
- A push that mixes ignored and deployable files triggers the job as normal. The ignored files are left out of the comparison.
- Optionally, the pipeline UI could show a skipped run with “only ignored files changed”, so it’s clear why nothing ran.
Example content of .gearsetignore:
docs/
*.md
.claude/
.prettierrc
package.json
package-lock.json