26 Feb, 2013

2 commits


19 Feb, 2013

1 commit


18 Feb, 2013

2 commits


14 Feb, 2013

1 commit

  • This option allows to disable users from changing their username.
    
    This is very usefull in environments using strong internal authentication methods like ldap, pam or shibboleth.
    
    You can allow users to change theyr username in these environments, but then new users (users loging in first time) is blocked from gitlab is her username exists.
    Jaakko Kantojärvi
     

13 Feb, 2013

2 commits


12 Feb, 2013

1 commit


31 Jan, 2013

1 commit


25 Jan, 2013

5 commits


24 Jan, 2013

3 commits


21 Jan, 2013

1 commit


18 Jan, 2013

1 commit


17 Jan, 2013

1 commit


07 Jan, 2013

1 commit


05 Jan, 2013

1 commit


04 Jan, 2013

1 commit


02 Jan, 2013

3 commits


30 Dec, 2012

1 commit


27 Dec, 2012

1 commit


14 Dec, 2012

1 commit


12 Dec, 2012

1 commit

  • The 2 reasons are :
    - creation of user fail if name is empty : in after_save, it tries to create a
    namespace with namespace.name = user.name and namespece validates presence
    Namespace#name
    - in the web app links to team members are broken with empty User#name because
    they are of the form <a href'...'> user.name </a>
    Cyril
     

29 Nov, 2012

3 commits


28 Nov, 2012

1 commit


25 Nov, 2012

2 commits


24 Nov, 2012

1 commit


23 Nov, 2012

2 commits