feat: speed up pushes for issue-to-mr by calling unshallow first
What does this merge request do and why?
Continues the work in !3815 (merged)
This MR makes the same changes to the issue-to-mr and developer flows.
How to set up and validate locally
- Set up Duo Agent Platform
- Set up the Flow Registry in your GDK
- Enable the new Duo Developer flow for Issue-to-MR:
Feature.enable :duo_developer_button - Run an issue-to-mr Flow
- Check your Flow Output in
Automate > Agent sessions:
Merge request checklist
-
Tests added for new functionality. If not, please raise an issue to follow up. -
Documentation added/updated, if needed. -
If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.
Edited by Roman Eisner
