Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(amazon q): adding view transformation summary to chat when code transformation complete and summary available #6257

Closed
wants to merge 3 commits into from

Conversation

ntarakad-aws
Copy link
Contributor

@ntarakad-aws ntarakad-aws commented Dec 16, 2024

Problem

We want to be able to have a button that is able to show the transformation summary when it is available. Currently the summary is automatically loaded when the proposed changes are downloaded.

Solution

In this way, we don't need to have the summary.md and associated icons in the proposed changes and the user can click on this button to view the transformation summary.


  • 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.

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.

@ntarakad-aws ntarakad-aws changed the title View summary feat(amazon q): adding view transformation summary to chat when code transformation complete and summary available Dec 16, 2024
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.

@dhasani23 dhasani23 closed this Dec 17, 2024
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.

2 participants