AppImage / AppImage/AppImageKit

Move to GitLab?

Ouverte
#803 26 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
deprioritized question
Langage dominant
Aucune donnée de langage
Étoiles
9.4k
Forks
588
Métriques de merge des PR
Métriques de PR en attente

Description

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?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.