The ultimate "How to make CI work with my fork" guide

Development
1
  1. Go to your fork : https://gitlab.kitware.com/username/vtk/
  2. Click on settings and expand Visibility

a
a894×1046 111 KB

  1. Click on Settings, CI/CD and expand General

b
b772×253 35.1 KB

  1. Rebase your branch in MRs against the last origin master
git fetch gitlab
git checkout master
git pull
git checkout your_branch
git rebase master
  1. Make sure to also pull the tags from origin master to avoid warnings
git fetch origin
git push gitlab --tags
4 Likes
2

@ben.boeckel feel free to improve

4

I cannot edit, but there is no reason to close and open a new MR; just amend and force push.

1 Like
5

I keep my fork master in synch with vtk master via pull and push commands from/to the two different repositories. Then I create feature/fix branches off my local master and only rebase them if necessary.

6

About closing and opening new MRs

Thanks I wasn’t sure about this one.

I keep my fork master in synch with vtk master via pull and push commands from/to the two different repositories. Then I create feature/fix branches off my local master and only rebase them if necessary.

Unrelated ?

7

With the current Gitlab interface:
2. Click on Settings then General. Expand Visibility
4. I cannot find this menu item anywhere

8

I can see it on my fork without issue, can you share a screenshot ?

9

I’m probably going to need to do it from work with a bigger monitor, but at least under the left menu I have:

image

10

Indeed. Maybe just dezoom with Ctrl + - ?

a
a356×574 19.1 KB

11

Maybe just scroll down :person_facepalming:

1 Like
12

I somewhat blame firefox and its hiding of scrollbars.

13

To be fair, Firefox is cargo culting this from elsewhere. Not sure why such terrible design decisions seem to be so contagious though.

16

This guide has been added to the official doc and should soon be available on the website: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/11428

17

@mwestphal thanks for letting me know.