MTA-7229 [DOC] Configuring repositories documentation is misleading#384
Conversation
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughDocumentation updates for three repository configuration procedures (Git, Maven, Subversion) shift the focus from general migration-task repository configuration to enabling insecure access via self-signed/internal certificates. Maven procedure steps and the rwx_supported constraint wording are also revised. ChangesRepository Access Documentation Rewrite
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@docs/topics/mta-ui/proc_configuring-maven-repo.adoc`:
- Around line 10-20: The warning about rwx_supported being false is too broad in
proc_configuring-maven-repo.adoc. Update the IMPORTANT note to state only that
the Local artifact repository and Clear repository controls are disabled when
RWX is off, while keeping the Administration > Repositories > Maven navigation
and the Consume insecure artifact repositories step available. Use the existing
{ProductShortName}, rwx_supported, Local artifact repository, and Clear
repository references to tighten the wording without changing the procedure
itself.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 6019ef1e-9e34-4c0e-95bd-f2217bfa5173
📒 Files selected for processing (3)
docs/topics/mta-ui/proc_configuring-git-repos.adocdocs/topics/mta-ui/proc_configuring-maven-repo.adocdocs/topics/mta-ui/proc_configuring-subversion-repos.adoc
|
@rromannissen Please could you check if the updates about insecure connection to repositories are accurate? Thanks much! |
|
|
||
| [role="_abstract"] | ||
| To allow {ProductFullName} to access the data required for migration tasks, configure *Git* repositories in the user interface (UI). By configuring these repositories, you enable {ProductShortName} to access your source code to identify modernization paths and required steps for your modernization efforts. | ||
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access the *Git* repository internal to your organization. |
There was a problem hiding this comment.
We must use this certain structure for procedures in terms of short descriptions:
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access the *Git* repository internal to your organization. | |
| As an Administrator, configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to your internal *Git* repository. |
|
|
||
| [role="_abstract"] | ||
| To give {ProductFullName} access to the data required for the migration tasks, configure *Maven* repositories in the user interface (UI). By configuring these repositories, you allow {ProductShortName} to access your source code to identify modernization paths and required steps for your modernization efforts. | ||
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access your *Maven* repository. |
There was a problem hiding this comment.
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access your *Maven* repository. | |
| As an Administrator, configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access your *Maven* repository. |
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access your *Maven* repository. | ||
|
|
||
| You can both configure a *Maven* repository and reduce its size in the *Repositories* view of the {ProductShortName} UI. | ||
| You can also clear the Maven cache of your local artifact repository in the *Repositories* view of the {ProductShortName} web console to save disk space. |
There was a problem hiding this comment.
I think we can skip "also" here. The sentence isn't directly related to the previous one
| You can also clear the Maven cache of your local artifact repository in the *Repositories* view of the {ProductShortName} web console to save disk space. | |
| You can clear the Maven cache of your local artifact repository in the *Repositories* view of the {ProductShortName} web console to save disk space. |
|
|
||
| [role="_abstract"] | ||
| To allow the {ProductFullName} to access the data required for the migration tasks, configure *Subversion* repositories in the user interface (UI). By configuring these repositories, you allow {ProductShortName} to access your source code to identify modernization paths and required steps for your modernization efforts. | ||
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access the *Subversion* repository internal to your organization. |
There was a problem hiding this comment.
| Administrators can configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to access the *Subversion* repository internal to your organization. | |
| As an Administrator, configure {ProductFullName} to accept self-signed or internal certificates to allow an insecure connection to your internal *Subversion* repository. |
mpershina
left a comment
mpershina
left a comment
There was a problem hiding this comment.
Added some suggestions
Signed-off-by: Prabha Kylasamiyer Sundara Rajan <pkylasam@redhat.com>
be4f3cc to
0dac5d6
Compare
3 participants
JIRA
Version
Previews
Summary by CodeRabbit