Adrian Lyjak b4bdcda384 fix(docs-sync): resolve developer-hub path to absolute before cd (#540) ...

The sync-docs-to-developer-hub.sh script accepts the developer-hub repo
path as its first argument. The CI workflow passes it as a relative path
(`developer-hub`) pointing to the checkout at the repo root. The markdown
rsync step ran before any `cd`, so the relative path resolved correctly,
but the mkdocs build step `cd`s into docs/api_docs first and then uses
the still-relative `$DOCS_REPO/api-reference/python/workflows` as its
output directory. mkdocs consequently wrote the built API reference to
`docs/api_docs/developer-hub/...` inside the source repo instead of into
the actual developer-hub checkout, so the subsequent
`git add api-reference/python/workflows/` found nothing to commit and
the API reference was never synced downstream.

Resolve $DOCS_REPO to an absolute path once up front so later `cd`s do
not change its meaning.

Co-authored-by: Claude <noreply@anthropic.com>

2026-04-15 01:09:52 +00:00

..

process_manifests.py

Add llama agents cli, serving, and deployment packages (#467)

2026-04-06 11:46:05 -04:00

sync-docs-to-developer-hub.sh

fix(docs-sync): resolve developer-hub path to absolute before cd (#540)

2026-04-15 01:09:52 +00:00