PR from original repository to forked repository

[bergamin]

This is related to #67. The feature I see in the task seems to be opposite to what they were asking for there. So I ask for some help. I may be missing something here. It seems the PR doesn't work from original repo to forked repo. Only the other way round.

This is how I set up my test task. It is going to be set up after the deploy phase of the original repository. The idea is that after the original repository is deployed, it should create a PR to update the forked repo, which is the one set up under "Repository":

But as the tooltip suggests, it uses the forked repo as the source and there is nothing I can do to swap source and target repos here

If there is now way to do it as of today, I suggest the option to choose which repos are going to be the source and target. If the fork or current repo

Thanks

Edit: task version is 1.*

[shayki5]

Hi @bergamin,
Thank you for opening this issue!
Yea, currently the "isFork" flag is from forked repo to the original which this is the common behavior.
I can add the opposite way as well but need time... have you thought about maybe trying to contribute?

[bergamin]

Hi, I could try, but I've never built a task for DevOps. I'm not even sure what language this is. I don't recognise this .ps1 filetype and I'm not quite sure how I could test it either... I'm not much into the MS development ecosystem nowadays. I do have a fallback license to an older version of Rider if this project needs .net, so I could try seeing if Rider recognises the project...

[shayki5]

Oh ok, the .ps1 it's PowerShell.
You can try play with that and open a PR and I can review and maybe fix.
I just don't work with Azure Pipeline these days so I don't know if I will have time to update this feature by myself...

[bergamin]

That's fair

[bergamin]

I solved my issue by reengineering my solution so I won't need this anymore. I'll keep the issue open in case anybody else would like to work on this

[shayki5]

Great, thank you!!