fix(ci): resolve clippy::indexing_slicing + doctest compile errors - #210
fix(ci): resolve clippy::indexing_slicing + doctest compile errors#210KooshaPari wants to merge 1 commit into
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 819d293c7a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| //! // The scenario is a script: the agent runtime reads it step by step. | ||
| //! let (steps, mock_llm) = scenario.into_mock_llm(); | ||
| //! assert_eq!(steps.len(), 4); // 2 user_says + 2 expect_tool_call | ||
| //! assert_eq!(mock_llm.remaining(), 3); // 3 mock responses queued |
There was a problem hiding this comment.
The newly added executable assertions extend a public Rust documentation code example, contrary to the repository's explicit requirement that documentation contain no code examples. Remove this block and describe the scenario/mock behavior in concise prose instead.
AGENTS.md reference: AGENTS.md:L117-L117
Useful? React with 👍 / 👎.
|
Closing as superseded. PR #211 has a cleaner cli.rs refactor (split_first(), while-let Some(flag) pattern). Doctest fix handled locally and will land separately. |
User description
Summary
CodeAnt-AI Description
Prevent command and mention parsing failures while keeping examples buildable
What Changed
Impact
✅ No crashes from malformed CLI or webhook input✅ Clear errors for missing command arguments✅ Buildable end-to-end testing documentation💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.