-
Notifications
You must be signed in to change notification settings - Fork 751
feat(amazonq): Adds capability to send new context commands to AB groups #6239
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
Conversation
|
9f9deb2 to
9103775
Compare
|
⛔️ Not planned for tomorrow's release. |
1c741c7 to
55e32df
Compare
| // @ts-ignore | ||
| let featureConfigs: Map<string, FeatureContext> = tryNewMap(featureConfigsSerialized) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why ignore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, this was existing code just moved up from lines 127 as you can see below. I can try and run a build without it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the annotation since this is now used in many places
55e32df to
c9b4746
Compare
|
…ws#6239) ## Problem When working on new features available to AB groups, the new action are not easily discoverable to users ## Solution Add the ability to send a new command that will appear when a user types @ in the chat window --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
…ws#6239) ## Problem When working on new features available to AB groups, the new action are not easily discoverable to users ## Solution Add the ability to send a new command that will appear when a user types @ in the chat window --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
…ws#6239) ## Problem When working on new features available to AB groups, the new action are not easily discoverable to users ## Solution Add the ability to send a new command that will appear when a user types @ in the chat window --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
…ws#6239) ## Problem When working on new features available to AB groups, the new action are not easily discoverable to users ## Solution Add the ability to send a new command that will appear when a user types @ in the chat window --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
Problem
When working on new features available to AB groups, the new action are not easily discoverable to users
Solution
Add the ability to send a new command that will appear when a user types @ in the chat window
feature/xbranches will not be squash-merged at release time.License: I confirm that my contribution is made under the terms of the Apache 2.0 license.