-
Notifications
You must be signed in to change notification settings - Fork 12
GitLab_Setup
TODO update this page for GUNN migration to github.com…
Click here for the ESGL GitLab sign in page, select the LDAP login and use your NDC credentials (the ESGL’s LDAP uses NDC). You won’t be able to sign in unless you have an ESGL or Tricklab account. If you have neither, then you should apply for an ESGL account:
Applying for ESGL account
You can get an ESGL account through the NASA NAMS system. In NAMS, search for “ESGL”, then select “JSC – ER7 – ESGL”. In the application options:
- For “ESGL Login Shell” select any. You don’t need a shell for GitLab since it’s web-based.
- For “ESGL Primary Group” you can select “No Primary Group”.
- For “Business Justification” say you need ESGL GitLab access to the GUNNS repositories for your work.
Once your ESGL access is granted, you can sign in to the ESGL Gitlab with the link at the top of this page.
GitLab arranges “projects” (git repositories) in “groups”, and users are given access to groups and thus all the projects within them. We have a public “gunns” group that gives everyone on the ESGL GitLab access to clone the GUNNS repositories. However, you need to be a member of the group in order to push updates to the repositories. Contact one of the GunnSmiths (contact info here) to request membership. Let us know what your ESGL account name is so we can find you in there.
By default, we’ll give you the “Reporter” role, which allows you to:
- clone the repositories,
- pull from any branch,
- write new issues in the issue tracker.
If you need to be able to push to non-protected branches, such as the next-project branch for your project, then let us know and we’ll give you the “Developer” role.
Within GitLab, see the Setup instructions in the gunns/gunns project page for your next steps.