NetworkManager/contrib
Thomas Haller 6c122534d6 automation: fetch NetworkManager's gitlab repository and add refs from merge-requests
Fetch both from github and gitlab, and also fetch the references for the
merge-requests/pull-requests.

In practice is github just a mirror of gitlab, so seemingly it wouldn't
make sense to fetch from there. However:

  - by adding github as a remote, we can preferably fetch from there.
    I think that is faster than our gitlab at freedesktop.org. Thank
    you, Microsoft!

  - pull requests against github are indeed not found in gitlab.

We need to fetch all kinds of remote references, so that the referenced
commits are in the git repository. Also, we need to fetch them under
various name, so that these references are available to CI.

For example, when someone opens a merge-request from their fork on
gitlab/github, the commit is usually not not referenced by regular
branches on gitlab/github. Hence, we couldn't schedule CI for those
commit. Also fetch the special references for these.

Also, don't use `timeout` to fetch the repository.
2019-10-03 13:54:23 +02:00
..
fedora makerepo: fix detection of parent commit for glib2 2019-05-15 08:18:22 +02:00
rh-bkr automation: fetch NetworkManager's gitlab repository and add refs from merge-requests 2019-10-03 13:54:23 +02:00
rh-jenkins contrib/jenkins: update jenkins_script.sh 2015-04-23 16:51:33 +02:00
rh-utils rh-utils: accept version number as argument for find-backports.sh 2018-11-22 11:38:09 +01:00