PR #7
Replies: 1 comment
-
|
akabr@akabarki76 MINGW64 / akabr@akabarki76 MINGW64 / akabr@akabarki76 MINGW64 / akabr@akabarki76 MINGW64 / akabr@akabarki76 MINGW64 ~ akabr@akabarki76 MINGW64 ~ akabr@akabarki76 MINGW64 ~/gemini-cli (my-feature) █████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
█████████ ██████████ ██████ ██████ █████ ██████ █████ █████ Tips for getting started:
╭─────────────────────────────────────────────╮ ✦ It looks like you've pasted an API key. For security reasons, please According to the project's GEMINI.md file, API keys should be stored I recommend deleting the message containing the key and storing it in ╭─────────╮ ╭───────────────────────────────────────────────────────────────╮ First, I'll create the directory. This command will create a new ╭──────────────────────────────────────────────────────────────────────────╮ ✦ I understand you're looking for guidance on how to contribute to this First, I'll examine the project's contribution guidelines to ensure we Contribution Tags (Conventional Commits) The project uses a standard called Conventional Commits. This is a Your commit message should be structured like this: 1 ():
Example: feat(cli): add --json flag to 'config get' command The Git Workflow (Pull, Commit, Push) To avoid conflicts and ensure you're working on the latest version of
Creating the "Perfect" Pull Request A "perfect" PR is one that is easy for maintainers to review and
By following these steps, you demonstrate respect for the project's Using 2 GEMINI.md files accepting edits (shift + tab to toggle) ~\gemini-cli no sandbox (see gemini-2.5-pro (98% context |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Creating the "Perfect" Pull Request
A "perfect" PR is one that is easy for maintainers to review and
understand.
linked to an existing issue. If one doesn't exist, create one first
and discuss the change before you start coding.
issue. Don't mix bug fixes, new features, and refactoring in the same
PR.
Conventional Commit format. The description should explain why you
made the change and link to the issue it solves (e.g., Fixes fix .env check google-gemini/gemini-cli#123).
feedback, open it as a "Draft Pull Request" on GitHub.
Make sure they are all green. This is a non-negotiable step.
with the CLI, you must update the documentation in the /docs
directory.
Beta Was this translation helpful? Give feedback.
All reactions