chore: expand common taskfile targets#494
Conversation
Detect the root Go module and Bun/Node targets so build, test, lint, and clean cover the runnable repo surfaces while skipping unavailable vendored docs dependencies. Co-authored-by: Codex <noreply@openai.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
codeant-ai
Bot
added
the
size:L
|
CodeAnt AI finished reviewing your PR. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 4 potential issues.
Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.
Reviewed by Cursor Bugbot for commit b64da9e. Configure here.
|
|
||
| for path in [Path("docs/.vitepress/cache")]: | ||
| if path.exists(): | ||
| shutil.rmtree(path) |
There was a problem hiding this comment.
clean:docs leaves vitepress build output behind
Low Severity
clean:docs only removes docs/.vitepress/cache and leaves docs/.vitepress/dist, which is the actual VitePress build output (uploaded as the deployable artifact in the docs CI workflow). This is inconsistent with the umbrella clean description ("Remove generated build artifacts") and with clean:chat, which removes both build outputs (.next, out) and caches (.turbo). After running task clean, stale docs build output persists.
Reviewed by Cursor Bugbot for commit b64da9e. Configure here.
| path.unlink() | ||
| elif path.is_dir(): | ||
| shutil.rmtree(path, ignore_errors=True) | ||
| shutil.rmtree(path) |
There was a problem hiding this comment.
Clean task no longer best-effort on errors
Low Severity
clean:go switched subprocess.run(..., check=False) to check=True and dropped ignore_errors=True from shutil.rmtree. If go clean returns non-zero (e.g. a locked cache) or an rmtree hits a transient permission/symlink issue, the task now aborts before removing the agentapi binary and the .cache/go-* directories, leaving stale artifacts that a clean invocation is expected to wipe.
Reviewed by Cursor Bugbot for commit b64da9e. Configure here.
| bun install --frozen-lockfile | ||
| fi | ||
| bun run build | ||
| ' |
There was a problem hiding this comment.
Chat install skipped when node_modules already exists
Low Severity
build:chat and lint:chat only run bun install --frozen-lockfile when chat/node_modules is absent. After a bun.lock or package.json update on an existing checkout, the directory still exists but holds stale dependencies, so bun run build/bun run lint execute against an out-of-date dependency tree without ever surfacing the lockfile mismatch.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit b64da9e. Configure here.
|
|
||
| for path in [Path("docs/.vitepress/cache")]: | ||
| if path.exists(): | ||
| shutil.rmtree(path) |
There was a problem hiding this comment.
clean:docs leaves vitepress dist output behind
Low Severity
clean:docs only removes docs/.vitepress/cache, but vitepress build emits its build output to docs/.vitepress/dist, which is the actual generated artifact a clean target is expected to remove. Similarly, clean:chat omits chat/storybook-static, even though build-storybook (and the .gitignore) treat it as generated output. The clean task therefore leaves stale build artifacts in the working tree.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit b64da9e. Configure here.
1 participant
User description
Detect the root Go module and Bun/Node targets so build, test, lint, and clean cover the runnable repo surfaces while skipping unavailable vendored docs dependencies.
Co-authored-by: Codex noreply@openai.com
Note
Low Risk
Build/test/lint/clean automation is broadened across Go and Bun/Node targets and could change local dev/CI behavior, but it does not affect runtime application logic.
Overview
Updates
Taskfile.ymlto run build/lint/clean across multiple detected targets (Go binary,chatBun project, anddocsNode build), with per-targetstatuschecks to skip tasks when dependencies/files aren’t present.Go tasks now use
GOCACHE+GOTMPDIR,lint:goenforcesgofmt(excludingagentapi-plusplus/**) and runsgo vetover all packages, andclean:goalso removes the new tmp/cache dirs. Adds dedicated cleaners forchat(.next,out,.turbo) anddocs(.vitepress/cache) and switches docs build tonpm ci --ignore-scripts.Reviewed by Cursor Bugbot for commit b64da9e. Bugbot is set up for automated code reviews on this repo. Configure here.
CodeAnt-AI Description
Expand common task commands to cover Go, chat, and docs targets
What Changed
chatapp is present, and docs build runs when the docs project is availableImpact
✅ Broader repo-wide build checks✅ Fewer task failures in partial checkouts✅ Cleaner local rebuilds🔄 Retrigger CodeAnt AI Review
Details
💡 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.