User Tools

Site Tools


gitlab:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
gitlab:start [2021/09/20 14:41] Yann Sagongitlab:start [2025/02/05 10:39] (current) – Fix internal link to Email address confirmation within the three days deadline paragraph Philippe Aepli
Line 1: Line 1:
- 
 ====== GitLab User Documentation ====== ====== GitLab User Documentation ======
  
Line 5: Line 4:
  
 <note important> <note important>
-See https://gitlab.unige.ch/help/user/index.md if you are looking for the upstream documentation of the UNIGE GitLab **running** instance.+See
 +  - https://gitlab.unige.ch/help/user/index.md if you are looking for the upstream documentation of the UNIGE GitLab **running** instance
 +  - https://catalogue-si.unige.ch if you need to contact the team behind GitLab.
 </note> </note>
 +
 +==== Learning ====
 +
 +Please see the UNIGE official formations at [[https://www.unige.ch/scicos/git-workshop|Source code management with Git]].
 +
 +
 ==== Access ==== ==== Access ====
  
Line 16: Line 23:
  
 Git ''clone/push/pull'' are available:  Git ''clone/push/pull'' are available: 
-  - via SSH (see https://gitlab.unige.ch/help/ssh/README.md ) after either the user has added a key in the GitLab profile settings or one of the project administrators has set up a **Deploy Key** in the GitLab project interface (see https://gitlab.unige.ch/help/user/project/deploy_keys/index.md )+  - via SSH (see https://gitlab.unige.ch/help/user/ssh ) after either the user has added a key in the GitLab profile settings or one of the project administrators has set up a **Deploy Key** in the GitLab project interface (see https://gitlab.unige.ch/help/user/project/deploy_keys/index.md )
   - via HTTPS after the user has generated a **Personal Access Token** in the GitLab profile settings (see https://gitlab.unige.ch/help/user/profile/personal_access_tokens.md ) or one of the project administrators has set up a **Deploy Token** in the GitLab project interface (see https://gitlab.unige.ch/help/user/project/deploy_tokens/index.md )   - via HTTPS after the user has generated a **Personal Access Token** in the GitLab profile settings (see https://gitlab.unige.ch/help/user/profile/personal_access_tokens.md ) or one of the project administrators has set up a **Deploy Token** in the GitLab project interface (see https://gitlab.unige.ch/help/user/project/deploy_tokens/index.md )
  
Line 47: Line 54:
 Please contact the UNIGE GitLab administrators (see https://catalogue-si.unige.ch/gitlab ) if you need more resources. Please contact the UNIGE GitLab administrators (see https://catalogue-si.unige.ch/gitlab ) if you need more resources.
  
 +<note important>
 +If you need to store **large** files such as audio, video or graphics ones, please consider switching to [[https://gitlab.unige.ch/help/topics/git/lfs/index.md|Git LFS]]!
 +</note>
 +
 +
 +==== Features =====
 +
 +The UNIGE GitLab instance is based on the upstream **Community Edition** (cf. https://about.gitlab.com/install/ce-or-ee/), since until now no Enterprise features have been needed after various evaluation.
 +
 +Of the CE-included feature, the UNIGE GitLab instance does not support the following ones:
 +  - CI/CD shared runners (cf. https://dataforum.unige.ch/t/gitlab-runners-not-available/401)
 +  - Pages (cf. https://dataforum.unige.ch/t/gitlab-pages-support/194)
 +  - PlantUML (cf. https://gitlab.unige.ch/help/administration/integration/plantuml.md via https://support-si.unige.ch/openentry.html?tid=INC000000146442)
  
 ==== Project visibility ==== ==== Project visibility ====
Line 52: Line 72:
 By default, each project is **private** , //i.e.// they can only be cloned and viewed by project members. By default, each project is **private** , //i.e.// they can only be cloned and viewed by project members.
  
-For more details, please check the [[https://gitlab.unige.ch/help/public_access/public_access|corresponding section]] of the upstream documentation of the UNIGE GitLab instance.+For more details, please check the [[https://gitlab.unige.ch/help/user/public_access|corresponding section]] of the upstream documentation of the UNIGE GitLab instance
 + 
 + 
 +==== How to validate your GitLab UNIGE email address ==== 
 + 
 +The link contained in the e-mail from the address ''GitLab <noreply-gitlab@unige.ch>'' sent to your email address is valid for three days. 
 + 
 +After this time, you must request a confirmation again by yourself. 
 + 
 +Please do not attempt to authenticate yourself by clicking on the ''Sign in'' link on this page! 
 + 
 +Here are the procedures for both cases: 
 + 
 +=== Email address confirmation within the three days deadline === 
 +  * open the confirmation e-mail with ''Confirmation instructions'' subject from ''GitLab <noreply-gitlab@unige.ch>'' 
 +  * click on ''Confirm your email address'' link 
 +    * here's an example of a confirmation link: 
 +<note tip> 
 +https://gitlab.unige.ch/-/profile/emails/confirmation?confirmation_token=<alpha_numeric_token> 
 +</note> 
 +  * you will be automatically authenticated and you will obtain the following message confirming your e-mail address validation: 
 +<note tip> 
 +Your email address has been successfully confirmed. 
 +</note> 
 + 
 +=== Email address confirmation after the three-day deadline === 
 +  * open the confirmation e-mail with ''Confirmation instructions'' subject from ''GitLab <noreply-gitlab@unige.ch>'' 
 +  * click on ''Confirm your email address'' link   
 +    * here's an example of a confirmation link:   
 +<note tip> 
 +https://gitlab.unige.ch/-/profile/emails/confirmation?confirmation_token=<alpha_numeric_token> 
 +</note> 
 +  * on this page you will obtain the following error message explaining that the deadline has been exceeded:   
 +<note warning> 
 +1 error prohibited this email from being saved: 
 +- Email needs to be confirmed within 1 day, please request a new one below 
 +</note> 
 +  * in the email field below error message, input again your email address to be confirmed 
 +  * click on the ''Resend'' button 
 +  * as soon you receive your new confirmation e-mail, follow the steps in the previous paragraph ([[gitlab:start#Email_address_confirmation_within_the_three_days_deadline|Email address confirmation within the three days deadline]]).
  
  
gitlab/start.1632148906.txt.gz · Last modified: 2021/09/20 14:41 by Yann Sagon