Re: GitLab migration update

[Uli Heilmeier <zeugs () heilmeier eu>]

Am 24.08.20 um 06:33 schrieb Gerald Combs:

> The issue creation script made the repository private in order to avoid rate limiting. If you do this through the web 
> interface, you're presented with a nice, clear warning that you'll sever the relationship of any forked repositories:
>
> https://docs.gitlab.com/ee/public_access/public_access.html#reducing-visibility
> https://gitlab.com/gitlab-org/gitlab/-/issues/33358
> https://gitlab.com/gitlab-org/gitlab/-/issues/22417
> https://gitlab.com/gitlab-org/gitlab/-/issues/19111
>
> If you do it from the API there's no warning. Unfortunately this means that if you were proactive an forked 
> https://gitlab.com/wireshark/wireshark then you either need to rename or remove your current repository and fork 
> again. Sorry about the hassle.

You don't have to do this. There is also the option to set "forked from" repository with an API call.

With httpie you have to call:
http POST 
'https://gitlab.com/api/v4/projects/<your-gitlab-username>%2Fwireshark/fork/7898047?access_token=<your-api-token>'

7898047 is the ID of https://gitlab.com/wireshark/wireshark

You can create the API Token in your gitlab user profile -> 'Access Tokens'. Before the call it could be necessary to
remove the fork relationship (Project settings -> General -> Advanced -> 'Remove fork relationship').


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe