Hi @jivanvl Nice work! I have some changes I would love to make.

• When I click Set up CI pipeline duo opens with this prompt on the chat Analyze this repository and generate a CI/CD pipeline Could we change the prompt to be Analyze repository to create a working and fully functional pipeline

• After the prompt is sent, Duo attempts to respond, but then nothing happens. Is this connected with the AI Agent we are building, or isn't it connected yet?

  

• When I see the responsiveness of the page it is acting weird.

  • Currently, when there isn't enough horizontal space to fit all actions in the repository toolbar (branch selector, Find file, Set up CI Pipeline, Code), the "Set up CI Pipeline" button is dropped entirely, while the other buttons remain in a weird order. The correct behavior should be - when the toolbar runs out of space, lower-priority actions should collapse into the existing overflow menu (the ... button). "Set up CI Pipeline" should be one of the hidden ones, but still accessible, not removed.

  • Project information should appear below the repository toolbar

    On desktop, Project information lives in the right sidebar, it's supplementary content. When the layout collapses to a single column, the repository toolbar (branch selector, Find file, Set up CI Pipeline, Code) should come first since it's what users act on. Project information should follow below it.

Let me know if you have any doubts!

@rayana wdyt? If I am not mistaken, this is a change leadership is pushing for: separating CI agents from CD agents, then having an orchestrator that calls both. I am not sure if we want to name it together anymore. Or am I mistaken?? cc: @manuelgrabowski @dhershkovitch

Hi @marcel.amirault if I am not mistaken, the plan is to have a CI agent and a CD agent. In the future, they will likely work together through a CI/CD agent that will call both of them, but right now, this is only for CI pipelines.

Yes, @manuelgrabowski everything is ready and confirmed! Maybe @marcel.amirault could review the CTA copy

No, it was a mistake. I updated it! cc @dhershkovitch

@anna_vovchenko I'd suggest going with Option 2. Since the user initiated this flow from the MR, their primary context is the MR, not the pipeline. Returning them to the MR pipelines tab keeps them in that context and lets them immediately see the result where it matters. If they want to drill into the pipeline details, it's only one click away. The consistency argument with branch pipelines doesn't quite apply here because the entry point and primary object are different. cc: @dhershkovitch @veethika

---

No concerns from the UX perspective, this makes sense!

Hi @jivanvl I made these for the entry points. I am still pending validation, but you can take a look in the meantime :). I will keep you posted! cc @veethika

Awesome! Approving now