-
Notifications
You must be signed in to change notification settings - Fork 55
Migrate Plexus-Interop project to FINOS organisation on GitHub #112
Comments
@maoo, @udalmik and @paulwhitby - This Friday 22nd May FINOS wants to transfer the Plexus Interop project from the This issue has been updated to reflect the change and to demonstrate how the transfer accounts for redirecting established relationships between the Plexus project, branches, forks, web hooks, developers and the wider Plexus engineering infrastructure. Please respond by thumbs up that you're aware of this work taking place and are in full agreement. |
Roger. Repo transfer is planned for Monday 25 May at 10am CEST . Note. The URL TODO - check backlinks on Google to understand where the URL is used. Thanks! |
The transfer is now done and the new repo URL is https://github.com/finos/plexus-interop Next ActionsThe following actions are being coordinated between @mcleo-d and @udalmik
|
@udalmik - I announced the Plexus-Interop repo transfer during the FINOS All Community call on 11th June and have marked as done on the following comment - #112 (comment) Can the remaining tasks also be marked as done ?
|
Description
This task describes migrating
plexus-interop
from thefinos-plexus
organisation into the primaryfinos
GitHub organisation following the migration ofplexus-interop-desktop-api
as described in issue #174.Solution
plexus-interop
from thefinos-plexus
organisation into thefinos
organisation on GitHub.plexus-interop
onfinos
.What's transferred with a repository?
https://help.github.com/en/enterprise/2.18/user/github/administering-a-repository/transferring-a-repository
When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
If the transferred repository is a fork, then it remains associated with the upstream repository.
If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
If the transferred repository uses Git Large File Storage, all Git LFS objects are automatically moved. This transfer occurs in the background, so if you have a large number of Git LFS objects or if the Git LFS objects themselves are large, it may take some time for the transfer to occur.
When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.
All links to the previous repository location are automatically redirected to the new location. When you use
git clone
,git fetch
, orgit push
on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:$ git remote set-url origin new_url
For more information, see Changing a remote's URL
The text was updated successfully, but these errors were encountered: