osc git staging plugin should fork to specific owner

[AdamMajer]

staging plugin users need to be able to specify the fork owner organiztion. For teams that work together, if they are able to create PRs from an org that they all have write access to, then they can update each other's PRs. Forking only to home is not a good idea in this case.

[AdamMajer]

Also, add a warning when fork organization is not specified and it default to private forks. Most staging work happens in teams and most of complaints is about access.

[dmach]

Can we reliably detect the org? E.g. where the devel project for a package lives?

[AdamMajer]

Maybe this is somethig that should be configured in the project git as some config file? Staging org is something. Then the staging plugin could try to use this.

Initially I thought that using env variable would be OK, but consider that someone could work as part of staging for TW for example, and also part of Leap staging and they would want to use different orgs.

You could use staging.config for this (add a field there) or create another file where this is placed.

[g7]

I think it being configurable in the git project (as said, staging.config or someplace else) would be nice, perhaps allowing it to be overridden via a command line option.

Being able to fork to a well-defined organization would be really helpful for us in RelEng at least, it is a bit of a pain point having to re-create PRs in order to rebase them if who created it is away.

[fwag]

I found this limitation in Gitea: go-gitea/gitea#36860 that prevents the implementation of this feature.