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

Bugfix/amazon q /doc: remove retry followup button and propose user instead New Task and End session to make it in sync with vscode plugin #5288

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vikshe
Copy link
Contributor

@vikshe vikshe commented Jan 22, 2025

Bugfix/amazon q /doc: remove retry followup button and propose user instead New Task and End session to make it in sync with vscode plugin

Types of changes

  • [ X ] Bug fix (non-breaking change which fixes an issue)

Description

remove retry followup button and propose user instead New Task and End session to make it in sync with vscode plugin.
Current logic for Retry button is not correct and it should retry previous operation, for now making it in sync with vscode plugin and it should be reviewed later

Checklist

  • [ X ] My code follows the code style of this project
  • I have added tests to cover my changes
  • [X ] A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@vikshe vikshe requested review from a team as code owners January 22, 2025 16:24
@vikshe vikshe marked this pull request as draft January 22, 2025 16:24
@vikshe vikshe force-pushed the bugfix/amazon-q-remove-retry-followup branch from b3ebc26 to d585e23 Compare January 22, 2025 21:08
@vikshe vikshe marked this pull request as ready for review January 22, 2025 21:11
…th vscode plugin. Instead propose user New Task and End session buttons
@vikshe vikshe force-pushed the bugfix/amazon-q-remove-retry-followup branch from 966ff07 to 81dc10d Compare January 23, 2025 15:46
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.

4 participants