Skip to content

Conversation

@iamsohilvahora
Copy link

Description

This PR documents the WP-CLI Contributor Badge process in the handbook.

Changes included

Related

Inspired by the Core AI Contributor Badge documentation.

@iamsohilvahora iamsohilvahora requested a review from a team as a code owner January 15, 2026 11:19
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @iamsohilvahora, 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 introduces comprehensive documentation for the WP-CLI Contributor Badge into the project handbook. The primary goal is to provide clear guidelines on how contributors can earn and display this badge on their WordPress.org profiles, thereby enhancing transparency and recognizing valuable contributions to the WP-CLI project.

Highlights

  • New Handbook Page: A new handbook page has been added specifically for the WP-CLI Contributor Badge.
  • Documentation of Process: The new page thoroughly documents the eligibility criteria and the assignment process for obtaining the WP-CLI Contributor Badge.
  • Official Association Link: The documentation includes a direct link to the official WordPress.org association page for WP-CLI contributors.
  • Manifest Update: The handbook-manifest.json file has been updated to correctly include and link to the newly added contributor badge page.
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 introduces documentation for the WP-CLI Contributor Badge, outlining the process for eligibility and assignment. The new handbook page is clear and informative. I've made a few suggestions to enhance formatting and add some useful links to improve the reader's experience.

Comment on lines +3 to +4
The **WP-CLI Contributor Badge** recognizes individuals who have made meaningful contributions to the WP-CLI project.
This badge is displayed on a contributor’s WordPress.org profile and highlights their involvement in maintaining and improving WP-CLI.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better readability and standard markdown practice, it's recommended to use a blank line to create a new paragraph instead of using two spaces for a hard line break.

Suggested change
The **WP-CLI Contributor Badge** recognizes individuals who have made meaningful contributions to the WP-CLI project.
This badge is displayed on a contributor’s WordPress.org profile and highlights their involvement in maintaining and improving WP-CLI.
The **WP-CLI Contributor Badge** recognizes individuals who have made meaningful contributions to the WP-CLI project.
This badge is displayed on a contributor’s WordPress.org profile and highlights their involvement in maintaining and improving WP-CLI.

Comment on lines +41 to +42
The official association page can be found here:
👉 https://profiles.wordpress.org/associations/cli-contributor
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For consistency and improved readability, it would be better to use a paragraph break (a blank line) to separate the introductory text from the link, instead of a hard line break.

Suggested change
The official association page can be found here:
👉 https://profiles.wordpress.org/associations/cli-contributor
The official association page can be found here:
👉 https://profiles.wordpress.org/associations/cli-contributor


If you are new to WP-CLI contributions:

- Read the [Contributing](https://make.wordpress.org/cli/handbook/contributions/) guide
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The link for the "Contributing" guide appears to point to the general "Contributions" index page. To provide a more direct path for users, consider updating it to link directly to the specific "Contributing" guide.

Suggested change
- Read the [Contributing](https://make.wordpress.org/cli/handbook/contributions/) guide
- Read the [Contributing](https://make.wordpress.org/cli/handbook/contributions/contributing/) guide


- Read the [Contributing](https://make.wordpress.org/cli/handbook/contributions/) guide
- Look for open issues in WP-CLI repositories
- Join a WP-CLI Hack Day or WordCamp Contributor Day
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To make it easier for new contributors to find relevant information, it would be helpful to add direct links to the "WP-CLI Hack Day" and "WordCamp Contributor Day" handbook pages.

Suggested change
- Join a WP-CLI Hack Day or WordCamp Contributor Day
- Join a [WP-CLI Hack Day](https://make.wordpress.org/cli/handbook/contributions/hack-day/) or [WordCamp Contributor Day](https://make.wordpress.org/cli/handbook/contributions/contributor-day/)

@swissspidy swissspidy linked an issue Jan 15, 2026 that may be closed by this pull request
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.

Document CLI contributor badge process

2 participants