Skip to content

Conversation

@JayanAXHF
Copy link
Owner

Ok so aarav is not here so i did it myself and this is how the api call will run and basically when youre done with the llm rachit js make it so that there is a function that can be called by the requests function to gen the output. ALSO PLEASE COMMIT THE CHANGES OF THE LLM IN THIS PR

@vercel
Copy link

vercel bot commented May 16, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
shiv-nadar ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 22, 2025 11:10am

@vercel
Copy link

vercel bot commented May 17, 2025

@DetectiveAK is attempting to deploy a commit to the jayanaxhf's projects team on Vercel, but is not a member of this team. To resolve this issue, you can:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Upgrade to pro and add @DetectiveAK as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here to upgrade and add @DetectiveAK as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the jayanaxhf's projects team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

@gitguardian
Copy link

gitguardian bot commented May 18, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
17229816 Triggered Hugging Face user access token 66a6c2f backend/llm/help2.ipynb View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@vercel
Copy link

vercel bot commented May 19, 2025

Someone is attempting to deploy this pull request to the jayanaxhf's projects Team on Vercel.

To accomplish this, the commit author's email address needs to be associated with a GitHub account.

Learn more about how to change the commit author information.

@JayanAXHF JayanAXHF merged commit c54dccd into main May 23, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants