Post 9rHmIBJrdodeE8sfia by winniehell@octodon.social
(DIR) More posts by winniehell@octodon.social
(DIR) Post #9rGzVDNkO80MdQHYa8 by rugk@social.wiuwiu.de
2018-06-02T11:52:51Z
0 likes, 1 repeats
#Github and #Microsoft… I think it is time to setup #GitLab mirrors, at least…If only one could also mirror the issues… ☹️I never found a good and easy way to mirror a whole GitHub repo. That includes issues, wiki, releases, etc.Could not GitLab or so integrate a "simple" switch for that? Best also vice versa – so #mirroring works in the other direction, too?
(DIR) Post #9rHmIBJrdodeE8sfia by winniehell@octodon.social
2020-01-23T07:24:58Z
0 likes, 0 repeats
@rugk slightly related: https://gitlab.com/gitlab-org/gitlab/issues/30672
(DIR) Post #9rHmU2DvHjbtUYko08 by winniehell@octodon.social
2020-01-23T07:27:09Z
0 likes, 0 repeats
@rugk Assuming that mirroring would also mean same issue numbers, what would be the expected behavior if two issues are created at the same time on GitHub and GitLab?
(DIR) Post #9rHmsrVWGT8HUnp5ay by rugk@social.wiuwiu.de
2020-01-23T07:31:39Z
0 likes, 0 repeats
@winniehellDunno, maybe just don't use the same issue numbers?🤔
(DIR) Post #9rHn72XM3Nt3l2RSzY by winniehell@octodon.social
2020-01-23T07:34:12Z
0 likes, 0 repeats
@rugk Also I know that Spam in issues has been a problem lately on gitlab.com. I assume for the mirroring you would have a bot account that transfers issue content. In that case you can no longer block the spam account because the bot happily transfers the stuff in its own name. 😬
(DIR) Post #9rHocYmkIzGihmEcwi by fin_ger@mastodon.social
2020-01-23T07:51:04Z
0 likes, 0 repeats
@rugk yesterday, I tried the gitea github migrator on codeberg... It horribly failed. Issues, PRs, etc. got imported, but where not assigned to the correct repository. Instead, all issues where randomly added to other projects 😭😭😭https://gitea.com/gitea/migratorAll 53 of my projects got screwed up...#gitea
(DIR) Post #9rIHR66lU0uHFYU8ga by paolo@mastodon.opencloud.lu
2020-01-23T11:09:32Z
0 likes, 0 repeats
@fin_ger Odd, I've mirrored but also copied over a few repositories on https://eugit.opencloud.lu and I haven't noticed the issue.I'll do some more testing to see if I can replicate your findings. @rugk
(DIR) Post #9rIHR6hzFcgH6ztrhg by fin_ger@mastodon.social
2020-01-23T11:14:28Z
0 likes, 0 repeats
@paolo @rugk I used this command with gitea-github-migrator 0.0.11+128 from the github releases downloads:gitea-github-migrator_linux_amd64 migrate-all --gh-user fin-ger --gh-token ... --url https://codeberg.org --token ...
(DIR) Post #9rIHR70Q95QU2AWaR6 by paolo@mastodon.opencloud.lu
2020-01-23T11:27:46Z
0 likes, 0 repeats
@fin_ger I always use the migration tool in the interface as AFAIK the command line tool is deprecated and hasn't been updated for nearly a year.Maybe you can do the same through API if you need to run something from a CLI? @rugk
(DIR) Post #9rIHR7Y67sMficHTvc by fin_ger@mastodon.social
2020-01-23T11:30:07Z
0 likes, 0 repeats
@paolo @rugk Hmm, I tried to use the Migration form on codeberg but could not figure out how it should work. All my imports via the migration form skipped issues, prs, etc.The form said I should just enter my github username to see further options, but no further options appeared...
(DIR) Post #9rIHR8AjoDGzeSML9k by paolo@mastodon.opencloud.lu
2020-01-23T11:44:37Z
0 likes, 0 repeats
@fin_ger I see they use version 1.10.3 while mine uses 1.10.2 maybe you found a regression?I've cloned one of the repository and the issue came up... without issues 🙂 @rugk
(DIR) Post #9rIHR8YUNuGuq7TJB2 by fin_ger@mastodon.social
2020-01-23T13:11:08Z
0 likes, 0 repeats
@paolo @rugk Oh no, I misunderstood the migration form 🙈 I thought the `Migrate` label indicates the form field for the github username...Sadly, the gitea FAQ points to the gitea-github-migrator tool which lead me in the wrong direction:https://docs.gitea.io/en-us/faq/#how-to-migrate-from-gogs-github-etc-to-gitea
(DIR) Post #9rIHR93KXEwSNltwFU by fin_ger@mastodon.social
2020-01-23T13:11:45Z
0 likes, 0 repeats
@paolo @rugk Also, Github informed me that using a password-based authentication for migration is deprecated:> You recently used a password to access an endpoint through the GitHub API using go-github. We will deprecate basic authentication using password to this endpoint soon:> We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
(DIR) Post #9rIHR9jW0OgaUbdd0C by fin_ger@mastodon.social
2020-01-23T13:13:03Z
0 likes, 0 repeats
@paolo @rugk Changing the password label to something like `API Token` and providing the above link to generate such a token would help users. I tested the migration with a PAT and it worked flawlessly.
(DIR) Post #9rIHRAA6PXx9p44rRY by rugk@social.wiuwiu.de
2020-01-23T13:13:56Z
0 likes, 0 repeats
@fin_gerSo? Send PR/MRs?@paolo
(DIR) Post #9rIJAsc05sDgfQUR4C by fin_ger@mastodon.social
2020-01-23T13:33:20Z
0 likes, 0 repeats
@rugk @paolo I submitted some issueshttps://github.com/go-gitea/gitea/issues/7635https://github.com/go-gitea/gitea/issues/9951