Skip to content

Conversation

@BlakeLazarine
Copy link
Contributor

Problem

Includes changes from this older PR #7696 which got reverted

Solution

re-do reverted changes

Renames QCodeReview tool to CodeReview

  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@BlakeLazarine BlakeLazarine requested review from a team as code owners July 21, 2025 23:39
@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@BlakeLazarine BlakeLazarine changed the title Code review tool fix(amazonq): fix finding suppression, change icon, change tool name Jul 22, 2025
@BlakeLazarine BlakeLazarine reopened this Jul 22, 2025
@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

modelSelection: true,
workspaceFilePath: vscode.workspace.workspaceFile?.fsPath,
qCodeReviewInChat: true,
codeReviewInChat: false,
Copy link
Contributor

Choose a reason for hiding this comment

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

why this is being renamed?

Copy link
Contributor

Choose a reason for hiding this comment

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

If yes, Did we do necessary changes in Flare?
Sticking to one name is advisable to avoid permutations and combinations in between VSC and Flare

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we were told to remove the q term in case q branding changes down the line

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah but this is internal code? We dont show this param to CX so its safe to use this!

If not we need to test with all the combinations.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

its been tested

Copy link
Contributor

Choose a reason for hiding this comment

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

Did we test with below scenarios

  • Old VSC + New Flare
  • New VSC + New Flare
  • Old VSC + Old Flare

@BlakeLazarine BlakeLazarine merged commit 61d328d into aws:master Jul 22, 2025
44 of 46 checks passed
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.

6 participants