Clarify workflow filename and config source in docs#8
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughUpdated documentation to treat Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
Removed mention of the root `groundkeeper.yml` as an example config.
Clarified instructions for creating configuration files.
There was a problem hiding this comment.
Pull request overview
This PR clarifies documentation about configuration file locations and workflow naming conventions in Groundkeeper.
Changes:
- Clarified that
.github/agent.ymlis the single source of truth for configuration, explicitly noting that legacygroundkeeper.ymlfiles are not used by the CLI or Action - Updated workflow filename examples from
maintenance.ymltogroundkeeper.ymlto align with the repository's actual convention, while noting that workflow filenames are flexible
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Updated workflow filename references and added explicit clarification about config file source of truth |
| QUICKSTART.md | Updated workflow filename reference and clarified config file location and usage |
Comments suppressed due to low confidence (1)
QUICKSTART.md:41
- The phrase "in your repository root" is misleading. The file
.github/agent.ymlis located in the.github/subdirectory, not in the repository root. Consider changing to "Create.github/agent.ymlin your repository" or "Create.github/agent.yml(in the.github/directory)".
Create `.github/agent.yml` in your repository root and validate it against `packages/schemas/agent.schema.json`:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Motivation
.github/agent.ymlas the single source of truth and that legacy/rootgroundkeeper.ymlfiles are not used..github/workflows/groundkeeper.yml).Description
README.mdto state that Groundkeeper reads.github/agent.ymlas the source of truth and that other example configs (such as a rootgroundkeeper.yml) are not used by the CLI or Action.README.mdandQUICKSTART.mdexamples to use.github/workflows/groundkeeper.ymland clarified that the workflow filename is flexible while noting the repo convention.Testing
Codex Task
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.