Augmenting contributing.md#2654
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 aims to improve the developer experience by providing detailed contribution guidelines and enhancing the robustness of error reporting within the application's multiprocessing components. The updated documentation will help new and existing contributors adhere to project standards, while the logging improvements will make it easier to diagnose and resolve issues by capturing more comprehensive error information. 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. Changelog
Activity
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. 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
|
There was a problem hiding this comment.
Code Review
This pull request significantly augments the CONTRIBUTING.md file with detailed guidelines for development, testing, and coding conventions, which will be very helpful for new contributors. It also improves error logging across several modules by replacing logger.error and logger.warning with logger.exception in except blocks, which will provide more context (including stack traces) when errors occur. My feedback includes a suggestion to clarify an installation instruction in the updated CONTRIBUTING.md to avoid confusion for new contributors.
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
Signed-off-by: KuntaiDu <kuntai@uchicago.edu>
* use logger.exception instead of logger.error to log stack trace Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * remove exception from logger.exception Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * augment contributing.md Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * revert non-CONTRIBUTING.md changes Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * make dco happy Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * trigger CI again --- git is failing Signed-off-by: KuntaiDu <kuntai@uchicago.edu> --------- Signed-off-by: KuntaiDu <kuntai@uchicago.edu> Co-authored-by: Samuel Shen <slshen@tensormesh.ai>
* use logger.exception instead of logger.error to log stack trace Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * remove exception from logger.exception Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * augment contributing.md Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * revert non-CONTRIBUTING.md changes Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * make dco happy Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * trigger CI again --- git is failing Signed-off-by: KuntaiDu <kuntai@uchicago.edu> --------- Signed-off-by: KuntaiDu <kuntai@uchicago.edu> Co-authored-by: Samuel Shen <slshen@tensormesh.ai> Signed-off-by: shaoxiawjc <wjc2800@163.com>
* use logger.exception instead of logger.error to log stack trace Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * remove exception from logger.exception Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * augment contributing.md Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * revert non-CONTRIBUTING.md changes Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * make dco happy Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * trigger CI again --- git is failing Signed-off-by: KuntaiDu <kuntai@uchicago.edu> --------- Signed-off-by: KuntaiDu <kuntai@uchicago.edu> Co-authored-by: Samuel Shen <slshen@tensormesh.ai> Signed-off-by: Aaron Wu <aaron.wu@dell.com>
* use logger.exception instead of logger.error to log stack trace Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * remove exception from logger.exception Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * augment contributing.md Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * revert non-CONTRIBUTING.md changes Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * make dco happy Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * trigger CI again --- git is failing Signed-off-by: KuntaiDu <kuntai@uchicago.edu> --------- Signed-off-by: KuntaiDu <kuntai@uchicago.edu> Co-authored-by: Samuel Shen <slshen@tensormesh.ai>
* use logger.exception instead of logger.error to log stack trace Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * remove exception from logger.exception Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * augment contributing.md Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * revert non-CONTRIBUTING.md changes Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * make dco happy Signed-off-by: KuntaiDu <kuntai@uchicago.edu> * trigger CI again --- git is failing Signed-off-by: KuntaiDu <kuntai@uchicago.edu> --------- Signed-off-by: KuntaiDu <kuntai@uchicago.edu> Co-authored-by: Samuel Shen <slshen@tensormesh.ai>
What this PR does / why we need it:
This PR augments the rules for contributing.md.
Special notes for your reviewers:
If applicable: