3 ms·
Thanks for using GitLab! While we can't disable pull requests on GitHub maybe we should add a feature to GitLab to keep importing these pull requests. For this
by sytse 10y ago
Thanks for using GitLab! While we can't disable pull requests on GitHub maybe we should add a feature to GitLab to keep importing these pull requests. For this we would need to create forks on GitLab or allow pull/merge requests from code on another server. Opinions are welcome.
- cm3 10y agoYes, automatic connectors would solve a lot. Some users might insist on a bidirectional solution, though it's not necessarily a requirement. In fact, I personally wouldn't want Gitlab to request permission to modify the github copy. At most, I would be okay with it subscribing to feeds and email-replying (no need to oauth) like any github user can. Speaking of disabling, if gitlab allowed disabling pull requests, wiki, issues, etc. and act like a pure git repo, it would solve a problem github refuses to address, namely a project's users wanting to use github/gitlab but the maintainer hosting the primary repo somewhere else. It would also play well with the D in DVCS, which github sort of breaks by leading users to centralize for convenience. I mean, one day github is down, another day gitlab, and so on, it's just how our networks operate.
- sytse 10y agoCool, I made an issue for the automatic import https://gitlab.com/gitlab-org/gitlab-ce/issues/21147 https://gitlab.com/gitlab-org/gitlab-ce/issues/21147 In GitLab you can already disable merge requests, wiki, and issues per project. See "Edit project".