<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=361395) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=361395) </details> <!--IssueSummary end--> This issue came out of this discussion https://gitlab.com/gitlab-org/gitlab/-/issues/358676#note_934072419. ### About The API endpoint that processes Slack events https://gitlab.com/gitlab-org/gitlab/-/issues/358676 is defined in `API::Integrations::Slack::Events` and the route is `api/v4/integrations/slack/events`. The older [API endpoint](https://gitlab.com/gitlab-org/gitlab/-/blob/0398c12b524e0542bb443005f9ffd865e36bbd85/ee/lib/ee/api/integrations.rb#L12) that processes Slack slash commands is related, but currently is defined in `API::Integrations` and the route is `api/v4/slack/trigger`. Without any breaking changes, we would like to rename the class and route of the slash commands endpoint to match the events endpoint. The benefits of this refactor is: - Improved code consistency. - Developers will understand the relationship more easily. - Aids code discoverability. ### Proposal - [ ] Move the definition of the API endpoint to a new `API::Integrations::Slack::SlashCommands` class. - [ ] Rename the route to `api/v4/integration/slack/slash_commands` (note: `slash_commands` and not `trigger`). - [ ] Redirect the old route to the new route. - [ ] Once deployed to .com: Update the GitLab (dev) Slack app and production Slack app to use the new route (don't publish the production Slack app)