fix: reorganize footer links under platform and community#2504
Conversation
Move About, VIP, and Branding under Platform, and Forums, Support, and Feedback under Community in footer page links. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the footer's information architecture to improve navigation clarity. By regrouping specific links under their more logical categories, the interface provides a more intuitive experience for users while maintaining existing access restrictions for VIP-only features. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
|
|
Overall Grade |
Security Reliability Complexity Hygiene Coverage |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| JavaScript | Jun 5, 2026 4:40a.m. | Review ↗ | |
| Code coverage | Jun 5, 2026 4:40a.m. | Review ↗ |
Code Coverage Summary
| Language | Line Coverage (Overall) |
|---|---|
| Aggregate | 67.2% |
| Javascript | 67.2% |
➟ Additional coverage metrics may have been reported. See full coverage report ↗
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
There was a problem hiding this comment.
Code Review
This pull request reorganizes the footer links in the PageLinks.svelte component. The 'About' and 'Branding' links have been moved from the community group to the platform group, while the VIP-restricted 'Support' and 'Feedback' links have been relocated from the platform group to the community group, with their display order also swapped. There are no review comments, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
This pull request updates the footer’s information architecture in the client app so links appear under the intended “Platform” and “Community” categories, aligning navigation labels with their grouped destinations.
Changes:
- Moved About and Branding links into the Platform footer group alongside VIP.
- Moved Forums (and the existing VIP-gated Support/Feedback links) into the Community footer group.
- Kept the Legal footer group unchanged.
Summary
This updates the footer information architecture so links appear under the intended categories. The goal is to make navigation labels match their section grouping.
Pull Request Checklist
Before you dim the lights and raise the curtain on your cinematic masterpiece,
make sure your pull request has passed these critical checks:
essence of your changes?
narrative that explains the "why" and "how" of your changes?
that showcases your changes in action?
tests to ensure it performs flawlessly under pressure?
ensuring it's as elegant as a film score?
the audience through the evolution of your code?
documentation accordingly?
eyes of the project maintainers and fellow contributors?