Rename "issue → MR" trigger to "duo-developer-flow"

Problem to solve

  • We have not revisited the naming of issue to MR flow since its development
  • Issue to MR flow should have the same consistent naming as the rest of our flows
  • Limited invocation surface: users can run the flow via an action button but cannot reliably trigger the same flow from comments/mentions

Proposal

  1. Canonical name
    • Rename the trigger to "duo-developer-flow" (display name: Duo Developer flow). Update code, configs, and docs to use the canonical name.
  2. Add Duo Developer/v1 to the sessions page.
  3. Comment mention trigger
    • Implement @duo-developer-flow as a case-insensitive, top-level comment trigger (must be on its own line). When posted on an issue or MR, it triggers the existing issue → MR flow for that resource and returns the same output as the action
  4. Button UX
    • Keep the existing action button initially. Whether to remove it later remains an open question for product to decide after telemetry/usage analysis.
  5. Docs & PMM
    • Update developer and user docs and PMM collateral to use the canonical name and document the @duo-developer-flow syntax and permissions.
  6. Backwards compatibility
    • Keep current behavior for existing triggers until documentation and code are updated to reference the new name

Open questions / decisions required

  • Whether/when to deprecate the action button.
Edited by Dasha Adushkina