chore: bootstrap FUNDING.yml and trufflehog.yml - #5
Conversation
Sorry, something went wrong.
Reduce README from 1124 to 169 lines (-85%). Keep: project name, description, quickstart, usage examples, why forge, installation, community, documentation link. Add fork disclaimer pointing to upstream tailcallhq/forgecode. Preserve all upstream content via pointer comment. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Sorry, something went wrong.
|
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 · |
Sorry, something went wrong.
|
Warning Rate limit exceeded@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 47 minutes and 54 seconds before requesting another review. 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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 1afc042a-a100-4e62-864a-57ae43681db7 📥 CommitsReviewing files that changed from the base of the PR and between b6e8c02 and 8180bd3. 📒 Files selected for processing (3)
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. ❤️ Share Review rate limit: 0/1 reviews remaining, refill in 47 minutes and 54 seconds.Comment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is ON, but it could not run because on-demand usage is turned off. To enable Bugbot Autofix, turn on on-demand usage and set a spend limit in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8180bd3. Configure here.
Sorry, something went wrong.
| @@ -0,0 +1,3 @@ | |||
| github: [KooshaPari] | |||
| custom: ["https://kooshapari.com/sponsor"] | |||
|
|
|||
There was a problem hiding this comment.
FUNDING.yml placed at repo root, not .github/
Medium Severity
FUNDING.yml is placed at the repository root, but GitHub only recognizes this file when located at .github/FUNDING.yml. A .github/FUNDING.yml already exists in this repo (with an empty sponsors list), so this root-level file will be silently ignored and the sponsor button won't reflect the intended KooshaPari GitHub sponsor or custom URL.
Reviewed by Cursor Bugbot for commit 8180bd3. Configure here.
Sorry, something went wrong.
| - "**/.git/**" | ||
| detectors: | ||
| - allowlist: false | ||
|
|
There was a problem hiding this comment.
Root trufflehog.yml config is never referenced by workflow
Low Severity
The trufflehog.yml config file at the repo root is unused. TruffleHog does not auto-discover config files — they must be passed explicitly via --config. The existing workflow at .github/workflows/trufflehog.yml runs trufflehog github --only-verified --no-update without a --config flag, so this configuration (scan depth, exclude paths, detector settings) will never take effect.
Reviewed by Cursor Bugbot for commit 8180bd3. Configure here.
Sorry, something went wrong.
| github: [KooshaPari] | ||
| custom: ["https://kooshapari.com/sponsor"] |
There was a problem hiding this comment.
🟠 Architect Review — HIGH
Funding links were added to a new root-level FUNDING.yml while this repo already has .github/FUNDING.yml, which is the file GitHub uses for the Sponsor button; as a result, the new KooshaPari sponsor configuration will not be picked up and the repository will continue using the older .github/FUNDING.yml settings.
Suggestion: Move or merge the new sponsor configuration into .github/FUNDING.yml and remove the duplicated root FUNDING.yml so there is a single authoritative funding file that GitHub will read.
Fix in Cursor | Fix in VSCode Claude
(Use Cmd/Ctrl + Click for best experience)
Prompt for AI Agent 🤖This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.
**Path:** FUNDING.yml
**Line:** 1:2
**Comment:**
*HIGH: Funding links were added to a new root-level FUNDING.yml while this repo already has .github/FUNDING.yml, which is the file GitHub uses for the Sponsor button; as a result, the new KooshaPari sponsor configuration will not be picked up and the repository will continue using the older .github/FUNDING.yml settings.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
Sorry, something went wrong.
|
CodeAnt AI finished reviewing your PR. |
Sorry, something went wrong.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge (already merged) Files Reviewed (3 files)
This PR adds repository metadata and configuration files:
All changes are documentation/configuration only with no impact on application code or runtime behavior. The changes are appropriate for repository housekeeping. Note: The PR has already been merged (closed with merge commit 406bc64). Reviewed by nemotron-3-super-120b-a12b-20230311:free · 377,685 tokens |
Sorry, something went wrong.
Reduce README from 1124 to 169 lines (-85%). Keep: project name, description, quickstart, usage examples, why forge, installation, community, documentation link. Add fork disclaimer pointing to upstream tailcallhq/forgecode. Preserve all upstream content via pointer comment. Co-authored-by: Phenotype Agent <agent@phenotype.ai> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
User description
Bootstrap FUNDING.yml and trufflehog.yml
Note
Low Risk
Low risk: adds repo metadata/config files and trims README content without touching application code or runtime behavior.
Overview
Repository housekeeping/metadata update. Adds FUNDING.yml with GitHub/custom sponsorship links and introduces trufflehog.yml to configure secret scanning (scan depth and excluded paths).
Docs change. Updates README.md to explicitly mark this as a Phenotype-org fork and point readers to upstream documentation, removing the large embedded usage/configuration sections from the README.
Reviewed by Cursor Bugbot for commit 8180bd3. Bugbot is set up for automated code reviews on this repo. Configure here.
CodeAnt-AI Description
Mark this repo as a Phenotype-org fork and move long docs out of the main README
What Changed
Impact
✅ Clearer project ownership
✅ Shorter README for faster scanning
✅ Easier sponsor and security setup
🔄 Retrigger CodeAnt AI Review
Details 💡 Usage GuideChecking 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.