Skip to content

docs: add new contributors section to contribution guidelines#10741

Open
saubyk wants to merge 1 commit intolightningnetwork:masterfrom
saubyk:update-code-contribution-guideline
Open

docs: add new contributors section to contribution guidelines#10741
saubyk wants to merge 1 commit intolightningnetwork:masterfrom
saubyk:update-code-contribution-guideline

Conversation

@saubyk
Copy link
Copy Markdown
Collaborator

@saubyk saubyk commented Apr 16, 2026

Advise new contributors to build a PR review track record before submitting code, or to open a detailed issue when they spot a bug.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, 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 project's contribution guidelines to introduce a new policy for new contributors. The goal is to encourage new developers to engage with the project through code reviews and detailed issue reporting rather than submitting code directly, helping to manage the influx of contributions in the era of AI-assisted coding.

Highlights

  • New Contributor Policy: Added a new section to the contribution guidelines that advises new contributors to build a PR review track record before submitting code.
  • Documentation Structure: Updated the table of contents in the contribution guidelines to include the new section.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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
Copy Markdown

@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 updates the code contribution guidelines to introduce a new policy for new contributors, requiring them to establish a track record of pull request reviews before submitting code due to the prevalence of AI-assisted tools. A review comment suggested grammatical and phrasing improvements to the new section to enhance readability and flow.

Comment thread docs/code_contribution_guidelines.md Outdated
Advise new contributors to build a PR review track record before
submitting code, or to open a detailed issue when they spot a bug.
@saubyk saubyk force-pushed the update-code-contribution-guideline branch from da8e129 to a05280e Compare April 16, 2026 23:03
@github-actions github-actions bot added the severity-low Best-effort review label Apr 16, 2026
@github-actions
Copy link
Copy Markdown

🟢 PR Severity: LOW

Automated classification | 1 file | 20 lines changed

🟢 Low (1 file)
  • docs/code_contribution_guidelines.md - documentation file under docs/*

Analysis

This PR modifies only a single documentation file (docs/code_contribution_guidelines.md). Documentation files under docs/* are classified as LOW severity per the classification rules. No code changes are present, and no severity bump conditions apply (1 file changed, 20 lines changed — well below the thresholds of 20 files or 500 lines).


To override, add a severity-override-{critical,high,medium,low} label.
<!-- pr-severity-bot -->

@hieblmi hieblmi self-requested a review April 17, 2026 08:26
Copy link
Copy Markdown
Collaborator

@hieblmi hieblmi left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Copy Markdown
Collaborator

@ziggie1984 ziggie1984 left a comment

Choose a reason for hiding this comment

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

Makes a lot of sense to restrict contributions more having seen a lot of AI-generated slope lately.


# New Contributors
Due to the general ubiquity of LLM tools available for coding, pull requests
from new contributors are not necessarily prioritized for review. If you're a
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Nit: remove necessarily or describe what you mean by it.

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.

3 participants