Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdds new MTA 8.1.0 release-notes assembly and three 8.1.0 topic pages, introduces an MTA 8.0 assembly, updates the master release-notes index to prioritize 8.1.0 and re-add 8.0, and makes small wording/format edits in several 8.0 topic files. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc`:
- Line 5: The document ID string "fixes-issues-8-1-0_{context}" is a typo and
should match the heading "Fixed issues"; update the ID to
"fixed-issues-8-1-0_{context}" so the identifier and heading are consistent
(locate the ID token "fixes-issues-8-1-0_{context}" and replace "fixes-issues"
with "fixed-issues").
🧹 Nitpick comments (1)
docs/topics/release-notes-topics/ref_removed-features-8-0.adoc (1)
14-14: Consider using explicit version for consistency.Line 14 uses the placeholder
{ProductVersion}while the abstract at line 9 uses the explicit version "8.0.0". For consistency within the document, consider using "8.0.0" explicitly here as well.📝 Suggested change for consistency
-In {ProductFullName} {ProductVersion}, XML rules are removed and are no longer supported both in the {ProductShortName} user interface (UI) and command-line interface (CLI). +In {ProductFullName} 8.0.0, XML rules are removed and are no longer supported both in the {ProductShortName} user interface (UI) and command-line interface (CLI).
Pkylas007
reviewed
Feb 24, 2026
Pkylas007
reviewed
Feb 24, 2026
Pkylas007
reviewed
Feb 24, 2026
Co-authored-by: Prabha Kylasamiyer Sundara Rajan <pkylasam@redhat.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc (1)
5-5: Document ID typo is now correctly resolved.The ID
fixed-issues-8-1-0_{context}now matches the= Fixed issuesheading. No further action needed here.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc` at line 5, Update the AsciiDoc anchor so it exactly matches the heading by replacing the placeholder id "fixed-issues-8-1-0_{context}" with the canonical id "fixed-issues-8-1-0" (so it aligns with the "= Fixed issues" heading); locate the id attribute in the docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc file (the id string "fixed-issues-8-1-0_{context}") and remove the "{context}" suffix so the anchor and heading match.
🧹 Nitpick comments (1)
docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc (1)
8-9: Stub file — ensure fixed-issue entries are added before merging.The abstract says "provides the following fixed issues," but the file contains no actual issue entries. This is expected for a [WIP] PR, but the content must be populated (e.g., a table or list of JIRA/BZ references with descriptions) before this file is merged to
main.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc` around lines 8 - 9, The abstract block marked with [role="_abstract"] currently claims "provides the following fixed issues" but contains no entries; populate this release-notes abstract by adding the fixed-issue entries (each with a JIRA/BZ identifier and a short description) either as a bulleted list or a table under that [role="_abstract"] paragraph, ensuring each entry references the ticket ID and a one-line summary and removing the WIP stub before merging.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc`:
- Line 9: Replace the phrase "other problems that have a significant impact"
with "other issues that have a significant impact" in the sentence that reads
"{ProductFirstRef} ({ProductShortName}) version 8.1.0 provides the following
fixed issues and other problems that have a significant impact." so the wording
is consistent with the section title and standard release-note style.
---
Duplicate comments:
In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc`:
- Line 5: Update the AsciiDoc anchor so it exactly matches the heading by
replacing the placeholder id "fixed-issues-8-1-0_{context}" with the canonical
id "fixed-issues-8-1-0" (so it aligns with the "= Fixed issues" heading); locate
the id attribute in the
docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc file (the id string
"fixed-issues-8-1-0_{context}") and remove the "{context}" suffix so the anchor
and heading match.
---
Nitpick comments:
In `@docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc`:
- Around line 8-9: The abstract block marked with [role="_abstract"] currently
claims "provides the following fixed issues" but contains no entries; populate
this release-notes abstract by adding the fixed-issue entries (each with a
JIRA/BZ identifier and a short description) either as a bulleted list or a table
under that [role="_abstract"] paragraph, ensuring each entry references the
ticket ID and a one-line summary and removing the WIP stub before merging.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adocdocs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc`:
- Line 51: Remove or replace the unfinished line "(Placeholder) Support for LLM
Proxying with MTA": either delete it entirely or replace it with a properly
formatted AsciiDoc entry that includes a clear heading, a brief descriptive body
of the feature, and a Jira reference/issue ID; ensure the new content follows
the surrounding release-notes structure (heading + paragraph or bullet points)
so it does not render verbatim in the published output.
- Line 30: The inline code span around `location,` incorrectly includes the
comma; update the text so the comma is outside the backticks (e.g., use
`location`, not `location,`) in the sentence referencing the csharp provider and
the rule fields (`pattern`, `location`, and `file_path`) used for
{ProductShortName} analysis.
- Line 21: The final clause mixes noun phrases with a prepositional phrase ("in
the UI, CLI, and by using the Visual Studio Code plugin"); make the list
parallel by using the same grammatical form for all items—e.g., replace that
clause in the sentence starting "Profiles contain analysis configuration..."
with a parallel phrase such as "via the UI, CLI, and Visual Studio Code plugin"
or "in the UI, in the CLI, and in the Visual Studio Code plugin" so all three
items match.
- Line 47: Remove the contradictory sentence "You can also use this extension
when you want to analyze a project in a specific programming language" and
eliminate the duplicate "You can also" by changing "Alternatively, you can also
download the {ProductShortName} Core extension..." to "Alternatively, download
the {ProductShortName} Core extension..." so the paragraph reads: the extension
pack description followed by the single-language alternative; edit the sentence
containing "You can also use this extension..." and the sentence starting
"Alternatively, you can also" accordingly.
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc (3)
51-51:⚠️ Potential issue | 🟠 MajorRemove or replace unfinished placeholder content before merge.
Line 51 still contains draft text:
(Placeholder) Support for LLM Proxying with MTA. This will render as-is in published release notes and should be replaced with final structured content (or removed).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc` at line 51, Replace or remove the unfinished placeholder text "(Placeholder) Support for LLM Proxying with MTA" in the release notes entry so it no longer renders as draft; either substitute it with the final structured release-note content (title, short description, impact, and any upgrade notes) for the "Support for LLM Proxying with MTA" item or delete that line entirely if the feature won't be included in this release.
21-21:⚠️ Potential issue | 🟡 MinorFix non-parallel phrasing in the tool list sentence.
Line 21 mixes forms in one list ("in the UI, CLI, and by using..."). Make all three items parallel for readability.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc` at line 21, The sentence "Migrators can sync with the {ProductShortName} Hub to download available configuration bundles and use them to run an analysis in the UI, CLI, and by using the Visual Studio Code plugin." uses mixed phrasing; make the three tools parallel by changing the final part to match the preposition style (e.g., "in the UI, in the CLI, and in the Visual Studio Code plugin" or better "via the UI, CLI, and Visual Studio Code plugin") so the list items are grammatically consistent; update that sentence in the document so all three items use the same form (prefer "via the UI, CLI, and Visual Studio Code plugin").
30-30:⚠️ Potential issue | 🟡 MinorMove the comma outside the inline code span.
At Line 30,
`location,`should be`location`with the comma outside backticks.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc` at line 30, The inline code span contains a trailing comma inside the backticks (`location,`) — move the comma outside the code span so the identifier remains `location` and the sentence punctuation follows it; update the text fragment referencing `pattern`, `location,` and `file_path` to read `pattern`, `location`, and `file_path` (i.e., remove the comma from inside the backticks and place it after the code span).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In
`@docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc`:
- Line 51: Replace or remove the unfinished placeholder text "(Placeholder)
Support for LLM Proxying with MTA" in the release notes entry so it no longer
renders as draft; either substitute it with the final structured release-note
content (title, short description, impact, and any upgrade notes) for the
"Support for LLM Proxying with MTA" item or delete that line entirely if the
feature won't be included in this release.
- Line 21: The sentence "Migrators can sync with the {ProductShortName} Hub to
download available configuration bundles and use them to run an analysis in the
UI, CLI, and by using the Visual Studio Code plugin." uses mixed phrasing; make
the three tools parallel by changing the final part to match the preposition
style (e.g., "in the UI, in the CLI, and in the Visual Studio Code plugin" or
better "via the UI, CLI, and Visual Studio Code plugin") so the list items are
grammatically consistent; update that sentence in the document so all three
items use the same form (prefer "via the UI, CLI, and Visual Studio Code
plugin").
- Line 30: The inline code span contains a trailing comma inside the backticks
(`location,`) — move the comma outside the code span so the identifier remains
`location` and the sentence punctuation follows it; update the text fragment
referencing `pattern`, `location,` and `file_path` to read `pattern`,
`location`, and `file_path` (i.e., remove the comma from inside the backticks
and place it after the code span).
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adocdocs/topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc
mpershina
commented
Feb 25, 2026
mpershina
commented
Feb 25, 2026
mpershina
commented
Feb 25, 2026
mguetta1
suggested changes
Feb 25, 2026
mguetta1
suggested changes
Feb 25, 2026
shawn-hurley
left a comment
shawn-hurley
left a comment
There was a problem hiding this comment.
I think for the most part this looks good, my only concern is that some of the language providers are not fully GA in the product yet but are tech-preview/dev-preview.
Co-authored-by: Maayan Hadasi <60384172+mguetta1@users.noreply.github.com>
mpershina
commented
Feb 27, 2026
mpershina
commented
Mar 4, 2026
mguetta1
approved these changes
Mar 4, 2026
Comment on lines
+54
to
+57
| * C# | ||
| * .NET | ||
| + | ||
| :FeatureName: Analyzing applications written in .NET |
Contributor
There was a problem hiding this comment.
I am not sure both C# and .NET extensions exist.
@savitharaghunathan @hhpatel14 could you please take a look?
There was a problem hiding this comment.
No, it's just one extension. I'd probably just call it C#
Collaborator
Author
There was a problem hiding this comment.
Thanks! Then I shall remove .NET from the docs (we have a couple of mentions within the docset)
eemcmullan
approved these changes
Mar 5, 2026
Pkylas007
reviewed
Mar 10, 2026
fabianvf
reviewed
Mar 10, 2026
mpershina
commented
Mar 17, 2026
mpershina
commented
Mar 17, 2026
mpershina
commented
Mar 17, 2026
mpershina
commented
Mar 18, 2026
mpershina
commented
Mar 18, 2026
dymurray
reviewed
Mar 20, 2026
dymurray
approved these changes
Mar 20, 2026
Contributor
dymurray
left a comment
dymurray
left a comment
There was a problem hiding this comment.
One request, aside from that LGTM
mpershina
commented
Mar 20, 2026
dymurray
approved these changes
Mar 23, 2026
anarnold97
reviewed
Mar 24, 2026
Co-authored-by: Andy Arnold <anarnold@redhat.com> Co-authored-by: Prabha Kylasamiyer Sundara Rajan <pkylasam@redhat.com>
mpershina
commented
Mar 24, 2026
anarnold97
reviewed
Mar 24, 2026
anarnold97
reviewed
Mar 24, 2026
Co-authored-by: Andy Arnold <anarnold@redhat.com>
anarnold97
reviewed
Mar 24, 2026
…ents-8-1-0.adoc Co-authored-by: Andy Arnold <anarnold@redhat.com>
Merged
This was referenced Apr 7, 2026
This was referenced Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document attributes PR: #300
Release notes preview: https://mpershina.github.io/Previews/MTA/8.1.0_RNs.html
Summary by CodeRabbit