docs: add new contributors section to contribution guidelines#10741
docs: add new contributors section to contribution guidelines#10741saubyk wants to merge 1 commit intolightningnetwork:masterfrom
Conversation
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 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 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 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 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 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
|
There was a problem hiding this comment.
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.
Advise new contributors to build a PR review track record before submitting code, or to open a detailed issue when they spot a bug.
da8e129 to
a05280e
Compare
🟢 PR Severity: LOW
🟢 Low (1 file)
AnalysisThis PR modifies only a single documentation file ( To override, add a |
ziggie1984
left a comment
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
Nit: remove necessarily or describe what you mean by it.
Advise new contributors to build a PR review track record before submitting code, or to open a detailed issue when they spot a bug.