13 Jun, 2013
2 commits
12 Jun, 2013
1 commit
06 Jun, 2013
1 commit
-
Authorize all teams to admin: fix 500 error on showing team page.
05 Jun, 2013
2 commits
-
500 error was occured in the following steps: 1. user1 creates new team "team1". 2. Assign team1 to project1. 3. Sign in as admin. This admin is not a member of team1. 4. Open project1 team setting page (/project1/team). 5. Click "team1" link in "Assigned teams" area. 6. 500 error. Fixed this issue.
04 Jun, 2013
1 commit
-
Conflicts: Gemfile.lock app/models/ability.rb app/models/project.rb app/views/snippets/_form.html.haml db/schema.rb features/steps/shared/paths.rb spec/factories.rb spec/models/project_spec.rb
03 Jun, 2013
1 commit
-
… if it exist in other owned project
27 May, 2013
1 commit
-
…itlabhq into dmedvinsky-add-defaults-create-group-team Conflicts: config/gitlab.yml.example
24 May, 2013
1 commit
16 May, 2013
1 commit
-
“Can create groups” and “Can create teams” had hardcoded defaults to `true`. Sometimes it is desirable to prohibit these for newly created users by default.
08 May, 2013
1 commit
06 May, 2013
1 commit
09 Apr, 2013
1 commit
-
…q into Undev-feature/refactoring_scopes_pr Conflicts: db/schema.rb
04 Apr, 2013
1 commit
03 Apr, 2013
2 commits
27 Mar, 2013
2 commits
26 Mar, 2013
1 commit
25 Mar, 2013
1 commit
24 Mar, 2013
1 commit
15 Mar, 2013
2 commits
13 Mar, 2013
1 commit
05 Mar, 2013
2 commits
-
State machine 3
04 Mar, 2013
1 commit
26 Feb, 2013
2 commits
19 Feb, 2013
1 commit
18 Feb, 2013
2 commits
-
Add option to disable username changing
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.
13 Feb, 2013
2 commits
12 Feb, 2013
1 commit
31 Jan, 2013
1 commit
25 Jan, 2013
2 commits