fix(DuoChat): Remove the 'clean' slash command
GitLab Integration MR: Remove clean slash command (gitlab!166979 - merged)
What does this MR do?
Resolves: DuoChat: Remove undocumented /clean command (#2788 - closed)
Removes all instances of /clean
command.
Screenshots or screen recordings
Behavior before: The behavior before is to not show /clean
as a slash command already. The correct slash command to return the UI back to it's original state is /clear
. The video below shows the UI in the integration branch NOT returning to it's original state when executing the /clean
command, which is the expected behavior.
Integration merge requests
-
GitLab: Remove clean slash command (gitlab!166979 - merged) -
JetBrains Extension: fix(JetBrains): Remove clean slash command (gitlab-org/editor-extensions/gitlab-jetbrains-plugin!1115 - merged) -
VSCode Extension: fix(Duo Chat): Remove clean slash command (gitlab-vscode-extension!2035 - merged) -
CustomersDot: mr_url -
Status Page: mr_url
Does this MR meet the acceptance criteria?
This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.
Toggle the acceptance checklist
Conformity
-
Code review guidelines. -
GitLab UI's contributing guidelines. -
If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer. -
If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer. -
If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above). -
Added the ~"component:*"
label(s) if applicable.
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
Security reports checked/validated by a reviewer from the AppSec team
Accessibility
If this MR adds or modifies a component, take a few moments to review the following:
-
All actions and functionality can be done with a keyboard. -
Links, buttons, and controls have a visible focus state. -
All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label
for icons that have meaning or perform actions. -
Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false"
toaria-expanded="true"
when an accordion is expanded. -
Color combinations have sufficient contrast.