You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2019. It is now read-only.
As part of the Great KiCad GitLab migration of 2019, I am testing the movement of open issues and PRs from GitHub to GitLab.
Here's what we know so far:
Open Pull Requests will transfer to GitLab without moving the source of the PR. That means pull requests will become GitLab Merge Requests that are referenced to the user's GitHub repository
Open Issues will transfer to GitLab issues
Closed/Resolved PRs and Issues will also transfer
In order to facilitate the transfer, it will be helpful if you can do two things:
Open a GitLab account (these can use your GitHub OAuth)
Set your GitHub email to public
Let me know who the responsible parties are for the Translation repository
The second point is critical because the migration script will only link users whose e-mail addresses match. If the script can't see your GitHub e-mail address, the issue will be tied to the KiCad-Bot that performs the migration.
The timeline for the actual migration will be determined by the responsible parties from bullet 3 above but it would greatly assist my testing for bugs if you could do the first two steps above as soon as possible.
Thank you-
Seth
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Translators-
As part of the Great KiCad GitLab migration of 2019, I am testing the movement of open issues and PRs from GitHub to GitLab.
Here's what we know so far:
In order to facilitate the transfer, it will be helpful if you can do two things:
The second point is critical because the migration script will only link users whose e-mail addresses match. If the script can't see your GitHub e-mail address, the issue will be tied to the KiCad-Bot that performs the migration.
The timeline for the actual migration will be determined by the responsible parties from bullet 3 above but it would greatly assist my testing for bugs if you could do the first two steps above as soon as possible.
Thank you-
Seth
The text was updated successfully, but these errors were encountered: