[Doc] Fix links to GH projects

[DarkLight1337]

Purpose

Missed in #27009

Test Plan

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[mergify]

Documentation preview: https://vllm--27530.org.readthedocs.build/en/27530/

[gemini-code-assist]

Code Review

This pull request fixes two broken links to GitHub Projects in the contributing guide by replacing a custom gh-project: scheme with full HTTPS URLs. My review suggests that while this fixes the links, a more maintainable approach would be to add support for the gh-project: scheme in the docs/mkdocs/hooks/url_schemes.py hook. This would centralize the link generation logic and keep the markdown source cleaner, addressing the root cause rather than applying a patch.

[gemini-code-assist]

While this change fixes the immediate issue of broken links, it replaces the concise gh-project: scheme with hardcoded, absolute URLs. This can make the documentation harder to maintain, especially if the project structure changes or if these links need to be updated across multiple files.

A more robust solution would be to enhance the documentation build process to handle the gh-project: scheme. This could be done by updating the docs/mkdocs/hooks/url_schemes.py hook to resolve these custom links into the correct GitHub project URLs. This approach would centralize the logic for URL generation, improve maintainability, and keep the Markdown source clean and consistent.

[hmellor]

Thanks for fixing, sorry I missed these!