-
Notifications
You must be signed in to change notification settings - Fork 653
Avoid hard-coding "quantum" in scripts/ scripts #1082
Copy link
Copy link
Open
Labels
area/devopsInvolves build systems, Make files, Bazel files, continuous integration, and/or other DevOps topicsInvolves build systems, Make files, Bazel files, continuous integration, and/or other DevOps topicshelp wantedHelp with this would be appreciatedHelp with this would be appreciatedno QC knowledge neededDoes not require knowledge of quantum computingDoes not require knowledge of quantum computingpriority/for-0.7.7To be done before releasing TFQ version 0.7.7To be done before releasing TFQ version 0.7.7
Metadata
Metadata
Assignees
Labels
area/devopsInvolves build systems, Make files, Bazel files, continuous integration, and/or other DevOps topicsInvolves build systems, Make files, Bazel files, continuous integration, and/or other DevOps topicshelp wantedHelp with this would be appreciatedHelp with this would be appreciatedno QC knowledge neededDoes not require knowledge of quantum computingDoes not require knowledge of quantum computingpriority/for-0.7.7To be done before releasing TFQ version 0.7.7To be done before releasing TFQ version 0.7.7
Type
Fields
Give feedbackNo fields configured for Task.
scripts/ci_validate_tutorials.shhas a hard-coded assumption that the user's local git working directory is named "quantum":This fails for developers who (like me) have multiple copies of the TFQ source tree, with different names for different concurrent development projects. Instead of assuming the directory is
quantum, the scripts in thescripts/directory should get the correct name using code such as the following: