Unify usage of AIRFLOW_REPO_ROOT in PMC testing docs

[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[jscheffl]

For me this is needed, else shellcheck will complaint.

Why do you think the quotes should be removed?

[amoghrajesh]

Guess it depends on the shell. I am doing this with reference to line 722 above: https://github.com/apache/airflow/pull/61238/changes#diff-1ef4f02ce0e55bffd7245e78c55bd83bfab647c6d4e6c8dc7925405398871371L722 to unify it

[jscheffl]

Guess it depends on the shell. I am doing this with reference to line 722 above: https://github.com/apache/airflow/pull/61238/changes#diff-1ef4f02ce0e55bffd7245e78c55bd83bfab647c6d4e6c8dc7925405398871371L722 to unify it

Okay, then according to shellcheck it should have quotes consistently. Else is whitespace in path (unlikely but possible) arguments are split.

[shahar1]

I think that we could settle on:

cd "$AIRFLOW_REPO_ROOT"

With quotes, without curly braces.

🙂

[amoghrajesh]

Yea seems like a good idea

[vincbeck]

LGM but please do not forget to update the title ;)

[amoghrajesh]

Yep, done!