Skip to content

docs: fix broken relative links in hackable_diffusion_adapter AGENT.md#706

Open
manumishra12 wants to merge 1 commit into
google-deepmind:mainfrom
manumishra12:docs/fix-agent-md-links
Open

docs: fix broken relative links in hackable_diffusion_adapter AGENT.md#706
manumishra12 wants to merge 1 commit into
google-deepmind:mainfrom
manumishra12:docs/fix-agent-md-links

Conversation

@manumishra12

Copy link
Copy Markdown

The links in gemma/diffusion/hackable_diffusion_adapter/AGENT.md use repo-root-relative paths, e.g.:

[`sft_sudoku.py`](gemma/diffusion/hackable_diffusion_adapter/configs/sft_sudoku.py)

GitHub resolves markdown links relative to the file containing them, so on the rendered page these resolve to a non-existent nested path (.../hackable_diffusion_adapter/gemma/diffusion/hackable_diffusion_adapter/configs/...) and return 404.

This PR makes the 9 links file-relative (e.g. configs/sft_sudoku.py) so they point to the files that already exist in the directory.

Change: documentation only — 9 links corrected, no content changes.
Verification: confirmed all 9 corrected paths resolve to existing files in the repo.

The links in AGENT.md used repo-root-relative paths (e.g.
gemma/diffusion/hackable_diffusion_adapter/configs/sft_sudoku.py). GitHub
resolves markdown links relative to the file's own directory, so these
resolved to a non-existent nested path and returned 404. Make them
file-relative (e.g. configs/sft_sudoku.py) so they point to the existing
files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant