Skip to content

fix(release): webhook env docs and feedback repo case matching - #431

Merged
devops-thiago merged 2 commits into
release/v0.5.0from
fix/v0.5.0-bugbot-feedback-env-docs
Jul 27, 2026
Merged

fix(release): webhook env docs and feedback repo case matching#431
devops-thiago merged 2 commits into
release/v0.5.0from
fix/v0.5.0-bugbot-feedback-env-docs

Conversation

@devops-thiago

@devops-thiago devops-thiago commented Jul 27, 2026

Copy link
Copy Markdown
Owner

What type of PR is this?

  • 🐛 Bug fix
  • ✨ Feature
  • 📝 Documentation
  • 🔧 Refactor
  • 🚀 Performance
  • ✅ Test
  • 🔒 Security
  • 📦 Dependency update
  • 🏗️ CI/CD

Description

Fixes two v0.5.0 Bugbot findings introduced by the structured-skip troubleshooting docs (#341) and finding-feedback dashboard filter (#324 / #423):

  • README troubleshooting checklist used non-existent WEBHOOK_TRIGGERS_* env vars. Operators following that guidance would set variables the app never reads (WEBHOOK_SKIP_DRAFTS, WEBHOOK_REQUIRED_LABELS, WEBHOOK_EXCLUDED_LABELS, WEBHOOK_BASE_BRANCHES, WEBHOOK_IGNORED_BASE_BRANCHES are the mapped names).
  • GET /api/dashboard/feedback?repository= authorized with case-insensitive repository access, then queried feedback with the raw query casing. Rows stored from webhooks (canonical GitHub casing) were missed when the filter casing differed. FindingFeedbackService.summarize / listRecent now match case-insensitively and return the stored repository key.

Related Issues

N/A — follow-up to #341 / #324 / #423 Bugbot findings on release/v0.5.0.

How Has This Been Tested?

  • Unit tests

  • Integration tests

  • Manual testing

  • ./mvnw -Dtest=FindingFeedbackServiceTest,DashboardResourceTest test — passed

  • New coverage: case-insensitive summarize/listRecent; dashboard feedback query with differing repository casing

Checklist

  • My code follows the project's coding standards
  • I have performed a self-review of my own code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly
  • My changes generate no new warnings or errors

Screenshots / Logs

N/A

Additional Notes

Targets release/v0.5.0 so the cut ships with correct operator docs and feedback filtering.

Align the troubleshooting checklist with the real WEBHOOK_* env vars, and
match dashboard feedback filters case-insensitively so access grants and
stored webhook casing stay consistent.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@thrillhousebot

Copy link
Copy Markdown

🤖 ThrillhouseBot PR Summary

What this PR does

This PR adds case-insensitive repository matching to the feedback summary and recent-feedback queries, updates the README troubleshooting checklist to use the correct webhook configuration environment variable names, and adds tests for the new case-insensitive behavior.

Changes Overview

  • Files changed: 4
  • Lines added: +69
  • Lines removed: -7

Changed Files

File Change Summary
README.md Modified Fixed webhook environment variable names in troubleshooting checklist
src/main/java/dev/thiagogonzaga/thrillhousebot/review/FindingFeedbackService.java Modified Changed summarize and listRecent queries to use lower(repository) = lower(?1) and return original casing
src/test/java/dev/thiagogonzaga/thrillhousebot/dashboard/DashboardResourceTest.java Modified Added integration test for case-insensitive repository query with dashboard endpoint
src/test/java/dev/thiagogonzaga/thrillhousebot/review/FindingFeedbackServiceTest.java Modified Added unit tests for case-insensitive matching in summarize and listRecent

Risk Assessment

Risk Count
🔴 Critical 0
🟠 High 0
🟡 Medium 0
🔵 Low 1

Key Findings

  • LOW: Non-deterministic repository casing in summarize due to unordered firstResultOptional (src/main/java/dev/thiagogonzaga/thrillhousebot/review/FindingFeedbackService.java:134)

⚠️ CI Checks Status

Some checks are still pending or have failed:

Check Type Status Detail
dependency-review check-run ⏳ Pending -

Automated review by ThrillhouseBot. Reply with /review to re-run.

@thrillhousebot thrillhousebot Bot added bug Something isn't working documentation Improvements or additions to documentation java Pull requests that update java code labels Jul 27, 2026
@codecov

codecov Bot commented Jul 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Order the case-insensitive lookup by repository so summarize returns a
stable casing when mixed-case rows exist.

Co-authored-by: Cursor <cursoragent@cursor.com>

@thrillhousebot thrillhousebot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

ThrillhouseBot found no issues in this PR, but some checks are still pending or failed:

  • Check actionlint is pending
  • Check format is pending
  • Check frontend is pending
  • Check trivy is pending
  • Check changes is pending
  • Check build is pending
  • Check test is pending
  • Check dependency-review is pending

@sonarqubecloud

Copy link
Copy Markdown

@devops-thiago
devops-thiago merged commit bd8629f into release/v0.5.0 Jul 27, 2026
16 checks passed
@devops-thiago
devops-thiago deleted the fix/v0.5.0-bugbot-feedback-env-docs branch July 27, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working documentation Improvements or additions to documentation java Pull requests that update java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant