What problem does this solve?
The export command currently only supports ignore patterns passed through the --ignore CLI option.
This means users must repeatedly provide the same ignore patterns every time they export a project, which is inconvenient for frequently exported repositories.
Proposed solution
Support a .scaffinityignore file in the project root.
The file should use standard .gitignore-style syntax and automatically be loaded during the export process.
CLI-provided --ignore patterns should continue to work and may optionally override or extend the patterns defined in .scaffinityignore.
Example:
node_modules
dist
.env
coverage
*.log
Usage:
No additional flags should be required.
Alternatives considered
Continue passing patterns through the --ignore option, but this becomes repetitive and harder to maintain across projects.
Would you be willing to open a PR for this?
What problem does this solve?
The
exportcommand currently only supports ignore patterns passed through the--ignoreCLI option.This means users must repeatedly provide the same ignore patterns every time they export a project, which is inconvenient for frequently exported repositories.
Proposed solution
Support a
.scaffinityignorefile in the project root.The file should use standard
.gitignore-style syntax and automatically be loaded during the export process.CLI-provided
--ignorepatterns should continue to work and may optionally override or extend the patterns defined in.scaffinityignore.Example:
Usage:
scaffinity exportNo additional flags should be required.
Alternatives considered
Continue passing patterns through the
--ignoreoption, but this becomes repetitive and harder to maintain across projects.Would you be willing to open a PR for this?