Skip to content

Fix 301 for MetaCPAN docs#1585

Merged
horgh merged 1 commit intomainfrom
greg/fix-metacpan-redirect
Feb 19, 2026
Merged

Fix 301 for MetaCPAN docs#1585
horgh merged 1 commit intomainfrom
greg/fix-metacpan-redirect

Conversation

@oschwald
Copy link
Member

No description provided.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Feb 19, 2026

Deploying dev-site with  Cloudflare Pages  Cloudflare Pages

Latest commit: 89ad014
Status: ✅  Deploy successful!
Preview URL: https://a7fac4af.dev-site-4ua.pages.dev
Branch Preview URL: https://greg-fix-metacpan-redirect.dev-site-4ua.pages.dev

View logs

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @oschwald, 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 with outdated links in the GeoIP web services documentation. Specifically, it updates the URLs for MetaCPAN references to the GeoIP2 Perl module, ensuring that users are directed to the correct and current resource path, thereby resolving potential 301 redirects.

Highlights

  • Documentation Update: Updated MetaCPAN links in the GeoIP web services documentation from /release/ to /dist/ to resolve 301 redirects.
Changelog
  • content/geoip/docs/web-services.md
    • Updated MetaCPAN links for the GeoIP2 Perl module to use the /dist/ path instead of /release/.
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

The pull request correctly updates the MetaCPAN links for the Perl (deprecated) client API to use the /dist/ path instead of /release/. This change addresses the 301 redirects as intended and ensures that users are directed to the canonical distribution page on MetaCPAN. The changes are consistent with the technical documentation standards of the repository.

@horgh horgh merged commit c7e19b2 into main Feb 19, 2026
10 checks passed
@horgh horgh deleted the greg/fix-metacpan-redirect branch February 19, 2026 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants