... | ... | @@ -94,7 +94,10 @@ Before leaving Inria: |
|
|
* the user ask for password recovery using the new identifier when the account has been converted and provide a new password.
|
|
|
|
|
|
## How to convert a user account from external to internal
|
|
|
External users can one day be hired by Inria and ask for an internal gitlab account. In this situation the external account can be converted into an internal one with proper inria email and iLDAP parameters. To do so the user must open a ticket (https://helpdesk.inria.fr/, section gitlab) requesting to convert the existing external account into an internal, providing the current external account login (e.g. x-Jdoe), the inria email and iLDAP login.
|
|
|
External users can one day be hired by Inria and ask for an internal gitlab account. In this situation the external account can be converted into an internal one with proper inria email and iLDAP parameters. To do so the user must open a ticket (https://helpdesk.inria.fr/, section gitlab) requesting to convert the existing external account into an internal one, providing:
|
|
|
* the current external account login (e.g. x-Jdoe),
|
|
|
* the inria email
|
|
|
* and the iLDAP login.
|
|
|
|
|
|
## How to activate a commit email hook
|
|
|
|
... | ... | |