Skip to content

Fix PR analysis workflow permissions#194

Open
SarthakKharche wants to merge 5 commits into
imDarshanGK:mainfrom
SarthakKharche:fix/pr-analysis-permissions
Open

Fix PR analysis workflow permissions#194
SarthakKharche wants to merge 5 commits into
imDarshanGK:mainfrom
SarthakKharche:fix/pr-analysis-permissions

Conversation

@SarthakKharche
Copy link
Copy Markdown

@SarthakKharche SarthakKharche commented May 21, 2026

Summary

Adds a GitHub Actions workflow (.github/workflows/pr-analysis.yml) that automatically runs QyverixAI code analysis on every pull request. The workflow detects changed .py, .js, and .ts files, sends each to the QyverixAI /analyze/ endpoint, and posts a formatted comment to the PR with scores, grades, and issues per file. If any file scores below 60, a needs-improvement label is automatically created and applied.

Fixes #130

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor

Testing

  • I ran backend tests (pytest -q)
  • I tested frontend behavior manually

Checklist

  • Code is readable and beginner-friendly
  • No fake or placeholder behavior introduced
  • Documentation updated if needed
image

@imDarshanGK
Copy link
Copy Markdown
Owner

@SarthakKharche Please update the PR with screenshots or implementation proof so the changes can be verified easily.
and link the related issue number in the PR description (example: Fixes #issue_number).

@SarthakKharche
Copy link
Copy Markdown
Author

@imDarshanGK
I have successfully edited the PR description with Fix Number. Also I have resolved the conflicts and have attached the screenshots of the work.
Please review it once.

Thank You

Copy link
Copy Markdown
Owner

@imDarshanGK imDarshanGK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SarthakKharche Please remove the hard dependency on QYVERIXAI_API_KEY or make it optional with a safe public default. The PR analysis action should work without extra secret setup, since the QyverixAI backend is already public-facing for this use case. Once that is fixed, I can re-review

@SarthakKharche
Copy link
Copy Markdown
Author

@imDarshanGK
I have updated it. Now QYVERIXAI_API_KEY is optional with a safe public fallback.
Plz review and merge it.

Thank You

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.

Build a GitHub Action that analyzes PRs automatically

2 participants