Move the Duo Agent Platform Triggers page to automations

Fiona Neillrequested to merge
636376-automations-redirect into master

Do not merge. This MR is held until the feature flag for the Triggers rebrand is enabled by default. It merges together with the rename MR stacked on top of it.

What does this MR do?

Moves the Duo Agent Platform Triggers page to a new path, as part of renaming triggers to automations:

  • Moves doc/user/duo_agent_platform/triggers/_index.md to doc/user/duo_agent_platform/automations/_index.md with no content changes, so reviewers can verify the move on its own.
  • Replaces the old page with a redirect to the new path.
  • Updates links to the page in the docs, the past release posts, the 19.1 "What's new" entry, and the in-app help link in flow_triggers_index.vue.

The content changes are in a separate MR that targets this MR's branch.

The remove_date of the redirect assumes this MR merges with the 19.6 release on 2026-11-19. Update it to three months after the actual merge date.

Related issues

Moving docs to a new location?

Read the redirect guidelines first.

  • Make sure the old link is not removed and has its contents replaced with a link to the new location.
  • Make sure internal links pointing to the document in question are not broken.
  • Search and replace any links referring to old docs in GitLab Rails app, specifically under the app/views/ and ee/app/views (for GitLab EE) directories. No links exist in those directories. The only link in the app is the helpPagePath in ee/app/assets/javascripts/ai/duo_agents_platform/pages/flow_triggers/index/flow_triggers_index.vue, which this MR updates.
  • Update the link in features.yml (if applicable).
  • Assign one of the technical writers for review.
  • Update data/en-us/navigation.yaml in docs-gitlab-com with the new path. That change is in a different project and isn't part of this MR.

Merge request reports