Skip to content

Update docs and tool description for read-many-files.#456

Merged
jacob314 merged 1 commit intomainfrom
jacob314/update_read_many_files_docs
May 20, 2025
Merged

Update docs and tool description for read-many-files.#456
jacob314 merged 1 commit intomainfrom
jacob314/update_read_many_files_docs

Conversation

@jacob314
Copy link
Contributor

Unsurprisingly this pull request was purely generated by GC after fixing a case where it messed up string escaping.
Feel free to suggest removing cases where this is overly verbose.

@jacob314 jacob314 merged commit 937f473 into main May 20, 2025
4 checks passed
@jacob314 jacob314 deleted the jacob314/update_read_many_files_docs branch May 20, 2025 23:32
'ReadManyFiles',
`Reads content from multiple text files specified by paths or glob patterns within a configured target directory and concatenates them into a single string.
`Reads content from multiple files specified by paths or glob patterns
within a configured target directory. For text files, it concatenates their content
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This goes over to the LLM we wont want to do line breaks here and below

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Removed line breaks within paragraphs. #476

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
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
hoteye added a commit to hoteye/gemini-cli that referenced this pull request Sep 17, 2025
Fixes google-gemini#8522

This commit restores comprehensive PR description parsing that was
accidentally removed in PR google-gemini#7698. The triage script now properly
detects issue references in PR descriptions using multiple patterns:

1. Direct references like "google-gemini#123"
2. Keyword patterns like "Closes google-gemini#123", "Fixes google-gemini#456", "Resolves google-gemini#789"
3. Fallback to GitHub's closingIssuesReferences API as last resort

Without this fix, ALL PRs were incorrectly labeled with status/need-issue
because the script could only detect GitHub's automatically detected
closing references, missing many valid manual references in descriptions.

The regression was introduced when PR description parsing logic was
removed, leaving only the GitHub API fallback which has limited coverage.
hoteye added a commit to hoteye/gemini-cli that referenced this pull request Sep 17, 2025
…itives

Per feedback from @srithreepo, remove direct google-gemini#123 pattern matching
to avoid incorrectly detecting issue references in cases like:
'Issue google-gemini#123 introduced this bug' which should still get needs-issue label.

Now only detects explicit closing keywords:
- Closes google-gemini#123
- Fixes google-gemini#456
- Resolves google-gemini#789
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`*
-->
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
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants