Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
GitLab instance: https://gitlab.eclipse.org/
GitLab has a similar functionality set compared to GitHub. A GitHub Pull Request is analogous to a a GitLab Merge Request. Below is a quick cheat sheet for getting productive with GitLab
- Global notification settings are in your profile: https://gitlab.eclipse.org/profile/notifications
- Group notificaton settings are also in your profile
- To "watch" a project, go to that project page. The notification bell at the top left can be changed to watch.
While project committers can commit to the repositories directly, contributors must use Merge Requests (MR). In fact, project committers can (should?) also use the Merge Request model to trigger code review.
There are many methods to trigger a Merge Request. They are all described here: https://gitlab.eclipse.org/eclipsefdn/gitlab/-/issues/25
- Currently no specific way to CC someone. See: https://gitlab.com/gitlab-org/gitlab/-/issues/197288
- you can @user1 in the comments, though. See: https://gitlab.eclipse.org/eclipsefdn/gitlab/-/issues/2#note_5
Migrating Git + Bugzilla to Gitlab: Please file an issue in Eclipse Foundation > Gitlab
Q: Big picture - what is involved in migrating a repository from github to gitlab?
A: First step is to cordinate the move with your community. Then, filing a Gitlab issue at https://gitlab.eclipse.org/eclipsefdn/gitlab/-/issues
Q:What is the learning curve for contributors?
A: As far as I can tell, it is close in functionality to Github.
Q: Are there contribution procedures in place for contributors to Eclipse projects?
A: The same ones as found at Github.
Q: Does ECA check work the same?