chore: add .venv and .vscode to .gitignore#2660
Conversation
Summary of ChangesHello @tae898, 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 enhances the repository's Highlights
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 adds common ignore patterns for Python virtual environments (.venv/) and VS Code (.vscode/) to the .gitignore file. This is a good practice. I've added one suggestion to ensure the file ends with a newline, which is a common convention for text files and improves compatibility with various tools.
|
thanks a lot! |
(cherry picked from commit bd2a3db)
What does this PR do?
Most Python and VS Code users have
.venv/and.vscode/directories in the Github repo root. And lately many systems add them to.gitignoreby default.Motivation
My VS Code thinks that changes are made but it's not. I just have my venv and vscode configured.