From 17b0088a5d41f898139d7976236dedd6180e6c3c Mon Sep 17 00:00:00 2001 From: Khaled Taymour Date: Sun, 15 Mar 2026 17:09:35 +0300 Subject: [PATCH] Fix broken STYLE_GUIDE.md references STYLE_GUIDE.md does not exist and never has in this repo. All three references to it were broken links: - CONTRIBUTING.md: Replace broken link with inline references to Google Python Style and Google TypeScript Style guides - .github/PULL_REQUEST_TEMPLATE.md: Point Style Guide link to CONTRIBUTING.md#coding-style - .gemini/styleguide.md: Point style section link to CONTRIBUTING.md#coding-style Co-Authored-By: Claude Opus 4.6 --- .gemini/styleguide.md | 2 +- .github/PULL_REQUEST_TEMPLATE.md | 2 +- CONTRIBUTING.md | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md index 0c7b7e46b..abeee7864 100644 --- a/.gemini/styleguide.md +++ b/.gemini/styleguide.md @@ -8,7 +8,7 @@ This style guide outlines the coding conventions for contributions to this repos Code should follow the relevant style guides, and use the correct auto-formatter, for each language, as described in -[the repository contributing guide's Style section](../STYLE_GUIDE.md). +[the repository contributing guide's Style section](../CONTRIBUTING.md#coding-style). ## Best Practices diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 1cba8aa99..7f60d0c6e 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -21,4 +21,4 @@ If you need help, consider asking for advice on the [discussion board]. [CLA]: https://cla.developers.google.com/ [Contributors Guide]: ../CONTRIBUTING.md [discussion board]: https://github.com/google/A2UI/discussions -[Style Guide]: ../STYLE_GUIDE.md +[Style Guide]: ../CONTRIBUTING.md#coding-style diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bd20995b8..027ac3a7e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -52,9 +52,9 @@ Here are some additional things to keep in mind during the process: To keep our codebase consistent and maintainable, we follow specific coding standards for Python and TypeScript. -Please refer to [STYLE_GUIDE.md](STYLE_GUIDE.md) for detailed guidelines on: -* **Python**: specific formatting, linting, and naming conventions (Google Python Style). -* **TypeScript**: usage of `gts`, naming conventions, and code organization (Google TypeScript Style). +Please follow these guidelines: +* **Python**: specific formatting, linting, and naming conventions ([Google Python Style](https://google.github.io/styleguide/pyguide.html)). +* **TypeScript**: usage of `gts`, naming conventions, and code organization ([Google TypeScript Style](https://google.github.io/gts/)). * **License Headers**: required copyright notices. We expect all contributors to adhere to these styles.