We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Common strategy is to have a 'schema' directory in the root of a repository.
However, using sem-add from the root puts the file in /scripts, rather than /schema/scripts
The text was updated successfully, but these errors were encountered:
One implementation of this would be to look for a:
".sem"
configuration file in the current working directory. If found, read the configuration and in there we'd have one key:
scripts_dir=./schema/scripts
By default this would be "./scripts" for backwards compatibility.
Any other thoughts for possible implementation?
Sorry, something went wrong.
Yeah, that was essentially my thought.
No branches or pull requests
Common strategy is to have a 'schema' directory in the root of a repository.
However, using sem-add from the root puts the file in /scripts, rather than /schema/scripts
The text was updated successfully, but these errors were encountered: