Skip to content

feat(gemini): enhance issue analysis with domain context, auto-labeli…#451

Open
vibhutikumar07 wants to merge 2 commits intodevelopfrom
gemini_fix
Open

feat(gemini): enhance issue analysis with domain context, auto-labeli…#451
vibhutikumar07 wants to merge 2 commits intodevelopfrom
gemini_fix

Conversation

@vibhutikumar07
Copy link
Collaborator

Describe your changes

  • Fix workflow: checkout@v4, correct bot-actor guard, add npm caching
  • Add edited trigger on gemini_issues_review.yml (fires only on body/title changes)
  • Add PROJECT_CONTEXT constant with full CAP SDM architecture details
  • Add classifyIssue() helper: auto-labels issues by type + component name
  • Guard against empty/short issue bodies with a structured info-request comment
  • Enrich analysis prompt with PROJECT_CONTEXT and classification result
  • Add priorAnalysis param to handleNewIssue for refined re-analysis passes
  • confirm remediation: now generates a task checklist from prior analysis
  • refine analysis: now fetches last bot comment as prior context before re-running
  • hey gemini on issues: now runs repo scan + injects PROJECT_CONTEXT for precise answers
  • Add edited event handler in run(): nudges for refine or runs fresh analysis

Any documentation

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

  • I follow Java Development Guidelines for SAP
  • I have tested the functionality on my cloud environment.
  • I have provided sufficient automated/ unit tests for the code.
  • I have increased or maintained the test coverage.
  • I have ran integration tests on my cloud environment.
  • I have validated blackduck portal for any vulnerability after my commit.

Upload Screenshots/lists of the scenarios tested

  • I have Uploaded Screenshots or added lists of the scenarios tested in description

…ng & edited trigger

- Fix workflow: checkout@v4, correct bot-actor guard, add npm caching
- Add edited trigger on gemini_issues_review.yml (fires only on body/title changes)
- Add PROJECT_CONTEXT constant with full CAP SDM architecture details
- Add classifyIssue() helper: auto-labels issues by type + component name
- Guard against empty/short issue bodies with a structured info-request comment
- Enrich analysis prompt with PROJECT_CONTEXT and classification result
- Add priorAnalysis param to handleNewIssue for refined re-analysis passes
- confirm remediation: now generates a task checklist from prior analysis
- refine analysis: now fetches last bot comment as prior context before re-running
- hey gemini on issues: now runs repo scan + injects PROJECT_CONTEXT for precise answers
- Add edited event handler in run(): nudges for refine or runs fresh analysis
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.

1 participant