Skip to content

Conversation

@yugalkaushik
Copy link
Contributor

@yugalkaushik yugalkaushik commented Jan 6, 2026

Description

  1. Ensures the Community page is reachable with and without a trailing slash in production, matching local behavior.
  2. In newcomers map the community link was hardcoded so fixed that
  3. In development config file redirect from plugin was missing so added that

This PR fixes #2523
Notes for Reviewers

Signed commits

  • Yes, I signed my commits.

@netlify
Copy link

netlify bot commented Jan 6, 2026

Deploy Preview for mesheryio-preview ready!

Name Link
🔨 Latest commit aa49f4c
🔍 Latest deploy log https://app.netlify.com/projects/mesheryio-preview/deploys/695d643af4986800082927ee
😎 Deploy Preview https://deploy-preview-2527--mesheryio-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yugalkaushik, 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 addresses an issue where the Community page was not consistently accessible in production when a trailing slash was used in the URL. By implementing a redirect, the page now behaves uniformly across different environments, improving user experience and resolving a known bug.

Highlights

  • URL Accessibility: The Community page (/community) now correctly handles requests with and without a trailing slash, ensuring /community/ redirects to /community.
  • Configuration Update: A redirect_from directive has been added to the front matter of the community.html page to manage the trailing slash redirection.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize 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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly resolves an issue where the community page was inaccessible with a trailing slash. By adding a redirect_from entry in collections/_pages/community.html, requests to /community/ will now properly redirect to the canonical /community URL. This is a standard and effective approach for Jekyll sites. The implementation is sound and I have no further suggestions.

@yugalkaushik
Copy link
Contributor Author

@kishore08-07 In the development configuration file, the redirect plugin was missing, so I added it as well, as its absence was causing redirect errors during development.

@yugalkaushik yugalkaushik changed the title fix: Community page: support both /community and /community/ Fix: community redirects and missing dev redirect plugin Jan 6, 2026
Copy link
Contributor

@Bhumikagarggg Bhumikagarggg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t think these three changes are necessary. @yugalkaushik, we’re aiming to keep this fix very minimal. This issue can be resolved with a much smaller change.

@yugalkaushik
Copy link
Contributor Author

@Bhumikagarggg among the three can you point out which one you found unnecessary and not minimal.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yugalkaushik Just remove '/' from this link https://meshery.io/community/. it will solve your issue.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the minimal fix but it won't solve the actual issue, hardcoding the link makes it irrelevant for development and preview. This is just one instance where trailing stash for community is causing 404 but there are multiple instances of community/ in the repo.

@CodexRaunak
Copy link
Member

@yugalkaushik Thank you for your contribution! Let's discuss this during the website call tomorrow at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken link in Newcomers map: Community Guide leads to page not found

3 participants