Repository navigation
Avoid hard-coding "quantum" in scripts/ scripts #1082
Description
scripts/ci_validate_tutorials.sh has a hard-coded assumption that the user's local git working directory is named "quantum":
cd ..
examples_output=$(python3 quantum/scripts/test_tutorials.py)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 the scripts/ directory should get the correct name using code such as the following:
thisdir=$(CDPATH="" cd -- "$(dirname -- "${0}")" && pwd -P)
repo_dir=$(git -C "${thisdir}" rev-parse --show-toplevel 2>/dev/null)Reacted by Aniket
Activity
Aniketsy commentedon Jun 5, 2026
I'll look into this and open PR shortly
SripriyaDevarapalli commentedon Oct 4, 2026
Hi! I'm interested in contributing to TensorFlow Quantum and would like to help with this issue. I understand that supporting significantly larger circuits may involve performance improvements across the circuit-processing or simulation workflow.
Could you suggest a specific, manageable part of this issue that would be suitable for a first contribution? I'd be happy to investigate the current bottlenecks, review the relevant code and tests, and submit a focused PR with benchmarks or tests where appropriate.
If this issue is still a priority, I'd appreciate your guidance on where I could make the most useful contribution. Thank you!