AppImage / AppImage/AppImageKit

Move to GitLab?

未關閉
#803 26 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
deprioritized question
主要語言
沒有語言資料
星號
9.4k
分支
588
PR 合併指標
PR 指標待擷取

描述

Now that GitHub is being acquired by Microsoft, we should consider to move our repositories to GitLab.

GitLab provides a tool for [#movingtogitlab](https://twitter.com/hashtag/movingtogitlab) but it does not take care of Travis CI.

![gitlab](https://user-images.githubusercontent.com/2480569/41189493-5db9dfa4-6bbe-11e8-9b91-86b63911422d.png)

And, as @Aztorius [writes](https://github.com/AppImage/appimage.github.io/pull/145#issuecomment-397890574) it is even possible to mirror the moved project back on GitHub:

> You can first import the GitHub project to GitLab. Then on GitLab, on the project page -> Settings -> Repository, "Push to a remote repository" you can add a link to the GitHub repo, something like : https://Aztorius:TOKEN@github.com/Aztorius/magicfountain.git where TOKEN is a Personal Access Token created on GitHub with public_repo access allowed.
More here : https://docs.gitlab.com/ee/workflow/repository_mirroring.html

GitHub writes:

> To set up your own mirror, you can configure a [post-receive hook](https://git-scm.com/book/en/Customizing-Git-Git-Hooks) on your official project repository to automatically push commits to a mirror repository on GitHub.com (or GitHub Enterprise)

without further details nor an example.

Main showstopper for migrating from GitHub to GitLab appear to be the `.travis.yml` that have been carefully nurtured over the years?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。