fix .env check - #123
Merged
Merged
Conversation
keithballinger
pushed a commit
that referenced
this pull request
Jun 13, 2025
yaleh
pushed a commit
to yaleh/gemini-cli
that referenced
this pull request
Jun 29, 2025
viridivn
pushed a commit
to viridivn/gemini-cli
that referenced
this pull request
Jun 29, 2025
FradSer
added a commit
to FradSer/gemini-cli
that referenced
this pull request
Jul 1, 2025
Replace rigid footer format validation with permissive approach: Removed Strict Validations: - No longer enforce exact patterns for issue references (e.g., 'Fixes google-gemini#123') - No longer require specific Co-authored-by format - Allow AI to use semantically correct alternatives Kept Essential Validations: - Reject extremely long footer lines (>200 chars) that indicate parsing errors - Catch empty BREAKING CHANGE declarations - Maintain basic structural sanity checks Benefits: - AI can use natural language variations like 'Fixes issue google-gemini#123' or 'Breaking change: ...' - Semantically correct footers are accepted regardless of exact format - Still protects against malformed content and parsing errors - More user-friendly for AI-generated commit messages Added test case demonstrating acceptance of flexible footer formats that are semantically correct but don't match rigid patterns. This prevents valid AI-generated footers from being unnecessarily rejected while maintaining protection against obvious errors.
gemini-cli
Bot
added
kind/enhancement
priority/p1
zapabob
pushed a commit
to zapabob/gemini-cli
that referenced
this pull request
Aug 1, 2025
主要機能: - グローバルインストールスクリプト (install-global.js) - 自然言語CLIエントリーポイント (naturalLanguageCli.js) - アンインストールスクリプト (uninstall-global.js) - バージョン管理機能強化 (version-manager.js) - 自動更新機能 (auto-updater.js) - 詳細エラーハンドラー (error-handler.js) - プログレスバー機能 (progress-bar.js) セキュリティ機能: - 電源断保護機能 (5分間隔自動保存) - 緊急保存機能 (Ctrl+C対応) - バックアップローテーション (最大10個) - セッション管理 (固有ID追跡) - リカバリーシステム (前回セッション復旧) 追加npmスクリプト (14個): - install:global, uninstall:global - version:current, version:update, version:check, version:changelog - update:check, update:auto, update:settings, update:history - error:analyze, error:system-info - progress:demo 技術的改善: - Commanderからyargsへの移行 - 型安全性の向上 - エラー分類システム (7種類) - セマンティックバージョニング対応 - 24時間間隔自動更新チェック テスト完了: - グローバルインストール成功 - gemini/gemini-naturalコマンド動作確認 - 全改善点機能動作確認 - 電源断保護機能動作確認 Closes: google-gemini#123 Related: google-gemini#456
hackeraum248-eng
added a commit
to hackeraum248-eng/gemini-cli
that referenced
this pull request
Sep 25, 2025
## TLDR <!-- Add a brief description of what this pull request changes and why and any important things for reviewers to look at --> ## Dive Deeper <!-- more thoughts and in-depth discussion here --> ## Reviewer Test Plan <!-- when a person reviews your code they should ideally be pulling and running that code. How would they validate your change works and if relevant what are some good classes of example prompts and ways they can exercise your changes --> ## Testing Matrix <!-- Before submitting please validate your changes on as many of these options as possible --> | | 🍏 | 🪟 | 🐧 | | -------- | --- | --- | --- | | npm run | ❓ | ❓ | ❓ | | npx | ❓ | ❓ | ❓ | | Docker | ❓ | ❓ | ❓ | | Podman | ❓ | - | - | | Seatbelt | ❓ | - | - | ## Linked issues / bugs <!-- Link to any related issues or bugs. **If this PR fully resolves the issue, use one of the following keywords to automatically close the issue when this PR is merged:** - Closes #<issue_number> - Fixes #<issue_number> - Resolves #<issue_number> *Example: `Resolves google-gemini#123`* **If this PR is only related to an issue or is a partial fix, simply reference the issue number without a keyword:** *Example: `This PR makes progress on google-gemini#456` or `Related to google-gemini#789`* -->
|
❌ Patch creation failed! There was an error creating the patch release. 🔍 Troubleshooting:
🔗 Links: |
|
❌ Patch Release Failed! 📋 Details:
🔍 Next Steps:
🔗 Troubleshooting: |
|
❌ Patch creation failed! There was an error creating the patch release. 🔍 Troubleshooting:
🔗 Links: |
|
❌ Patch Release Failed! 📋 Details:
🔍 Next Steps:
🔗 Troubleshooting: |
|
❌ Patch creation failed! There was an error creating the patch release. 🔍 Troubleshooting:
🔗 Links: |
|
❌ Patch Release Failed! 📋 Details:
🔍 Next Steps:
🔗 Troubleshooting: |
anowardear062-svg
approved these changes
Oct 31, 2025
aka1976mb
added a commit
to aka1976mb/gemini-cli
that referenced
this pull request
Nov 28, 2025
Co-authored-by: riddhi <duttariddhi@google.com> ## Summary <!-- Concisely describe what this PR changes and why. Focus on impact and urgency. --> ## Details <!-- Add any extra context and design decisions. Keep it brief but complete. --> ## Related Issues <!-- Use keywords to auto-close issues (Closes google-gemini#123, Fixes google-gemini#456). If this PR is only related to an issue or is a partial fix, simply reference the issue number without a keyword (Related to google-gemini#123). --> ## How to Validate <!-- List exact steps for reviewers to validate the change. Include commands, expected results, and edge cases. --> ## Pre-Merge Checklist <!-- Check all that apply before requesting review or merging. --> - [ ] Updated relevant documentation and README (if needed) - [ ] Added/updated tests (if needed) - [ ] Noted breaking changes (if any) - [ ] Validated on required platforms/methods: - [ ] MacOS - [ ] npm run - [ ] npx - [ ] Docker - [ ] Podman - [ ] Seatbelt - [ ] Windows - [ ] npm run - [ ] npx - [ ] Docker - [ ] Linux - [ ] npm run - [ ] npx - [ ] Docker
4 tasks
ChickensLord8
added a commit
to ChickensLord8/gemini-cli
that referenced
this pull request
Dec 29, 2025
## Summary Centered all README content including title, badges, screenshot, and description text to improve visual presentation and professional appearance of the project documentation. ## Details Wrapped the main README content in a `<div align="center">` tag to center-align all elements. This creates a more polished, modern look for README and improves the first impression for new users and contributors. ## Related Issues <!-- Use keywords to auto-close issues (Closes google-gemini#123, Fixes google-gemini#456). If this PR is only related to an issue or is a partial fix, simply reference the issue number without a keyword (Related to google-gemini#123). --> ## How to Validate 1. Navigate to the README.md file on GitHub 2. Verify that the title "Gemini CLI" is centered 3. Confirm all badges are centered horizontally 4. Check that the screenshot image is centered 5. Verify the description text is centered 6. Test rendering on both light and dark GitHub themes 7. Check mobile responsiveness (optional) ## Pre-Merge Checklist - [x] Updated relevant documentation and README (if needed) - [ ] Added/updated tests (if needed) - [ ] Noted breaking changes (if any) - [ ] Validated on required platforms/methods: - [ ] MacOS - [ ] npm run - [ ] npx - [ ] Docker - [ ] Podman - [ ] Seatbelt - [ ] Windows - [ ] npm run - [ ] npx - [ ] Docker - [ ] Linux - [ ] npm run - [ ] npx - [ ] Docker
18 tasks
This was referenced Jan 24, 2026
This was referenced Jan 24, 2026
Closed
Closed
18 tasks
6 tasks
6 tasks
MadelineStrong
referenced
this pull request
in MadelineStrong/gemini-cli
Apr 17, 2026
…eneral (#25586)
Co-authored-by: JAYADITYA <96861162+JayadityaGit@users.noreply.github.com> Co-authored-by: Jack Wotherspoon <jackwoth@google.com>
## Summary
<!-- Concisely describe what this PR changes and why. Focus on impact and
urgency. -->
## Details
<!-- Add any extra context and design decisions. Keep it brief but complete. -->
## Related Issues
<!-- Use keywords to auto-close issues (Closes #123, Fixes #456). If this PR is
only related to an issue or is a partial fix, simply reference the issue number
without a keyword (Related to #123). -->
## How to Validate
<!-- List exact steps for reviewers to validate the change. Include commands,
expected results, and edge cases. -->
## Pre-Merge Checklist
<!-- Check all that apply before requesting review or merging. -->
- [ ] Updated relevant documentation and README (if needed)
- [ ] Added/updated tests (if needed)
- [ ] Noted breaking changes (if any)
- [ ] Validated on required platforms/methods:
- [ ] MacOS
- [ ] npm run
- [ ] npx
- [ ] Docker
- [ ] Podman
- [ ] Seatbelt
- [ ] Windows
- [ ] npm run
- [ ] npx
- [ ] Docker
- [ ] Linux
- [ ] npm run
- [ ] npx
- [ ] Docker
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.