EPMRPP-115237 || Move encryption logic to service-api#6
Conversation
|
Warning Review limit reached
More reviews will be available in 8 minutes and 54 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThe PR migrates the encryption abstraction from ChangesGitHub Auth Plugin – Encryptor migration and plugin rename
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@build.gradle`:
- Around line 38-39: The service-api dependency for both implementation and
annotationProcessor declarations is pinned to a JitPack commit hash (771a360)
instead of a stable semantic version from ReportPortal's official releases.
Replace the commit hash with a stable release version number (such as 5.14.0 or
later) in both the implementation and annotationProcessor entries for
com.github.reportportal:service-api to ensure API stability and proper support
for the IntegrationParamsEncryptor class that is actively used throughout the
codebase.
In `@src/main/java/com/epam/reportportal/extension/github/GitHubExtension.java`:
- Line 78: The PLUGIN_NAME constant in the GitHubExtension class is set to
"GitHub OAuth" while the pluginName property in gradle.properties is set to
"GitHub Auth", causing the plugin to have two different public identities. To
fix this, align the PLUGIN_NAME constant value in GitHubExtension to match the
pluginName value defined in gradle.properties, or vice versa, ensuring both
locations reference the same display name for the plugin.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 083da2d2-07c6-4008-aefb-00dada1b7a13
📒 Files selected for processing (4)
build.gradlegradle.propertiessrc/main/java/com/epam/reportportal/extension/github/GitHubExtension.javasrc/main/java/com/epam/reportportal/extension/github/service/GitHubIntegrationStrategy.java
…strictions method and remove unused constants
Summary by CodeRabbit