Skip to content
New issue

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

Avoid littering git repository when running locally #3

Open
avillar opened this issue Oct 20, 2022 · 3 comments
Open

Avoid littering git repository when running locally #3

avillar opened this issue Oct 20, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@avillar
Copy link
Collaborator

avillar commented Oct 20, 2022

Files generated/modified by update_vocabs.py are tracked by git, which is necessary when running the pipelines but gets confusing when working locally.

@avillar avillar added the enhancement New feature or request label Oct 20, 2022
@avillar
Copy link
Collaborator Author

avillar commented Oct 20, 2022

@rob-metalinkage, I have added an output directory argument to the script. We can now run it locally like this:

python -m ogc.na update_vocabs.py -o build <rest of args>

and all new files (validation outputs, entailed files) will be put under that build subdirectory, recreating the path structure from the working directory (e.g., definitions/x/y.ttl is entailed into build/definitions/x/entailed/y.ttl). We could also use an external directory (like /tmp/build).

When running from the pipe, we just leave the output directory option out, and it works like it always has.

@avillar avillar self-assigned this Oct 20, 2022
@rob-metalinkage
Copy link
Collaborator

Good idea.. we can revisit if we need to test redirection to these locally... but that is a bigger issue to consider.

@avillar
Copy link
Collaborator Author

avillar commented Oct 20, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants