AI_code-reviewer

Important: Repository History Rewritten

During the initial upload, the .env file (containing secret keys) was accidentally committed. To remove secrets from the repository, the commit history was rewritten and the cleaned main branch was force-pushed to the remote. As a result, commit SHAs changed.

If you previously cloned or forked this repository, sync to the rewritten main branch with one of these options:

• Re-clone the repository (simplest and safest):

  git clone https://github.com/Aprabin98/AI_code-reviewer.git

• Or, update an existing clone (this will discard local changes on main):

  git fetch origin git checkout main git reset --hard origin/main

After syncing, rotate any secrets that were stored in .env (API keys, tokens, etc.). The .env file is now ignored via .gitignore to prevent future leaks.

If you need help syncing or preserving any local branches, contact the repository owner before taking destructive commands.

to use this in you other repi maile yo ucheej hary garna parxa to remember i am pasting this

🚀 How to Enable AI Code Reviews on a Repository

Since the AI Code Reviewer engine is permanently running in the cloud, you can attach it to any repository in less than 60 seconds without redeploying any code.

Step 1: Grant Repository Access (If applicable)

• If you own the repository: Skip to Step 2 (the bot already has access through your account).
• If someone else owns the repository: They must invite your GitHub username as a Collaborator under their repository's Settings -> Collaborators. You must accept the invitation before the bot can post comments.

Step 2: Set Up the Webhook on GitHub

1. Go to the target repository on GitHub and click the Settings tab.
2. In the left-hand sidebar, click Webhooks, then click the Add webhook button.
3. Configure the webhook with these exact settings:
   • Payload URL: https://ai-code-reviewer-56b5.onrender.com/api/webhook
   • Content type: Select application/json (Crucial!)
   • Secret: Enter your configured webhook secret string (live_github_secret_98`).
   • SSL verification: Leave enabled.

Step 3: Select the Trigger Events

1. Under "Which events would you like to trigger this webhook?", select Let me select individual events.
2. Uncheck the Pushes box.
3. Scroll down and Check the Pull requests box.
4. Leave everything else unchecked.
5. Click the green Add webhook button at the bottom of the page.

🎯 How to Test It

1. Open a new branch in that repository.
2. Make a small code change, commit it, and push it to GitHub.
3. Open a Pull Request (PR).
4. Within a few moments, the background cloud worker will pick up the PR event, analyze the diff using Gemini, and automatically post a detailed 🛡️ Security and 🎨 Style review directly as a comment on the PR!