git multi-remote configuration

もっと見る

PHASES OF THE PROGRAMMING PROCESS

BERNAL CONTRERAS BERNAL CONTRERASにより

Pathways to Land Tenure

owen taylorにより

ASSIGNMENT 3.1 Defending North America

taylor hにより

Shunra/Cloud

Benny Daonにより

generic user/developper

Atlas cluster or FS's laptop

CIT or cWB team laptops

GitLab@aei.uni-hannover.de: AEI remote

aei branch1

GitLab@ligo.org: LSC remote

cWB/library

lsc branch1

master

GitLab.com: private/public remote

What I propose:

Phase 0

1. Creation of GitLab.com "shared" repository with private settings, i.e. visible and usable just by cWB team, with some branches of cWB to be shared (FS)

Phase 1

1. Testing on atlas and on my laptop (FS)
2. Testing at CIT and on LSC/Virgo members laptops (GV, SK, etc)
3. A lot of work (merging, pruning old stuff, documenting).....

Phase 2

1. Creation of GitLab.com "public" repository, i.e. visible and accessible to everyone (though, obviously, just the development team will be allowed to do commits).
2. Add a licence

Note: all technical items, such as creation of the GitLab repository or adding a new remote and new branches to existing repositories are super easy (and have been tested on a dummy repository already)!

cWB/library public

public

cWB/library private

shared1