致力于
- 作者仓库星标 2,483
- 许可证 MIT
- 作者仓库 node-google-spreadsheet
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @theoephraim · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Bun
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
You are given an issue or external PR to implement. The input may be a URL, pasted issue text, or pasted PR diff/description.
**Input:** $ARGUMENTS
## Workflow
Follow these steps in order:
### 1. Understand the task
- If given a URL, fetch it to read the issue/PR details.
- Analyze the issue or PR to understand what needs to be done.
- Summarize the task back to the user and confirm before proceeding.
### 2. Create a branch
- Create a descriptive branch name based on the task (e.g., `fix/cell-formatting-bug`, `feat/add-batch-update`).
- Branch from `main`.
### 3. Implement the changes
- Make the necessary code changes.
- Follow existing code patterns and conventions in the project.
### 4. Add or update tests
- Add tests for the new functionality or bug fix in `src/test/`.
- Follow existing test patterns — tests are integration tests that hit real Google APIs.
- If modifying existing behavior, update relevant existing tests as needed.
- To validate, only run the relevant test file(s) to avoid rate limiting: `bun vitest run src/test/<relevant-file>.test.ts`
- Do NOT run the full test suite.
### 5. Update documentation
- If your changes affect the public API (new methods, changed parameters, new features, etc.), update the relevant docs in `docs/`.
- Class API docs are in `docs/classes/` (one file per class: `google-spreadsheet.md`, `google-spreadsheet-worksheet.md`, `google-spreadsheet-row.md`, `google-spreadsheet-cell.md`).
- Guides are in `docs/guides/`.
- The sidebar is `docs/_sidebar.md` — update it if adding a new page.
- Match the style and format of the existing documentation.
### 6. Lint
- Run `bun run lint:fix` to auto-fix any lint issues.
- If lint errors remain, fix them manually.
### 7. Add a changeset
- Run `bun changeset` — since this is interactive, instead create the changeset file directly.
- Create a `.changeset/<descriptive-name>.md` file with the appropriate format:
```
---
"google-spreadsheet": <patch|minor|major>
---
<Short description of the change>
```
- Use `patch` for bug fixes, `minor` for new features and non-breaking changes, `major` for breaking changes.
### 8. Commit and push
- Stage and commit all changes with a clear commit message.
- Push the branch to origin.
### 9. Create a PR
- Use `gh pr create` to open a pull request.
- Write a clear title and description summarizing the changes.
- If the input was a GitHub issue, reference it in the PR body (e.g., "Fixes #123").
- Return the PR URL to the user.
章节与文件索引
按说明文件中的顺序排列。
工作流程
1. 理解任务
2. 创建分支
3. 实施变更
4.添加或更新测试
文件/命令 -> fix/cell-formatting-bug · feat/add-batch-update · main · src/test/ · bun vitest run src/test/<relevant-file>.test.ts · docs/ · docs/classes/ · google-spreadsheet.md
内容校验值 -> 004549b64a69
当前原文的自动摘译,尚未人工审校。
工作流程
按顺序执行以下步骤:
1. 理解任务
如果给定了 URL,请获取它以阅读问题/PR 详细信息。分析问题或 PR 以了解需要做什么。将任务总结回用户并确认后再继续。
2. 创建分支
根据任务创建描述性分支名称(例如,
fix/cell-formatting-bug、feat/add-batch-update)。来自main的分支。3. 实施变更
进行必要的代码更改。遵循项目中现有的代码模式和约定。
4.添加或更新测试
在
src/test/中添加新功能的测试或错误修复。遵循现有的测试模式——测试是针对真正的 Google API 的集成测试。如果修改现有行为,请根据需要更新相关的现有测试。要进行验证,请仅运行相关测试文件以避免速率限制:bun vitest run src/test/<relevant-file>.test.ts不要运行完整的测试套件。