- 21 Jul, 2014 1 commit
-
-
Ayrton Araújo authored
-
- 26 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 13 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 30 May, 2014 1 commit
-
-
Jeroen van Baarsen authored
This setting was not longer used in GitLab, so i think it can be removed. Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 23 Apr, 2014 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 19 Apr, 2014 1 commit
-
-
Dmitri Moore authored
-
- 15 Apr, 2014 1 commit
-
-
Cyril Rohr authored
-
- 11 Apr, 2014 1 commit
-
-
Robert Schilling authored
-
- 07 Apr, 2014 1 commit
-
-
Marin Jankovski authored
-
- 31 Mar, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 25 Jan, 2014 1 commit
-
-
Jason Hollingsworth authored
A test was broken if running on a non-standard port. Made checking for (non-)standard port more robust. Changed gitlab_on_non_standard_port to gitlab_on_standard_port (less negative).
-
- 09 Dec, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Before this commit gitlab-shell but me placed directly in home dir. Ex: /home/git/gitlab-shell After this change you can place gitlab-shell in custom location. Ex: /Users/developer/gitlab/gitlab-shell Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 29 Nov, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 Nov, 2013 1 commit
-
-
Jason Hollingsworth authored
Added visibility_level icons to project view (rather than just text). Added public projects to search results. Added ability to restrict visibility levels standard users can set.
-
- 01 Oct, 2013 1 commit
-
-
Sytse Sijbrandij authored
-
- 22 Sep, 2013 2 commits
-
-
Izaak Alpert authored
Change-Id: I02814fb47edcc915309183547cc8dcb165100f4f
-
Izaak Alpert authored
GITLAB-1262 Change-Id: I690cb8ea294df53ebe8405a519c23c501af2c21a Conflicts: app/models/user.rb config/initializers/1_settings.rb spec/models/user_spec.rb
-
- 09 Sep, 2013 1 commit
-
-
Angus MacArthur authored
-
- 25 Aug, 2013 1 commit
-
-
ash wilson authored
Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown references in descriptions, titles, or attached Notes creates a back-reference Note that links to the original referencer. Furthermore, pushing commits with commit messages that match a (configurable) regexp to a project's default branch will close any issues mentioned by GFM in the matched closing phrase. If accepting a merge request would close any Issues in this way, a banner is appended to the merge request's main panel to indicate this.
-
- 21 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Jul, 2013 1 commit
-
-
Izaak Alpert authored
-If not specified in the gitlab.yml default this setting to false Change-Id: I3551df364498dd84ccbd18c90797522e77159f05
-
- 23 May, 2013 1 commit
-
-
Mitch Tishmack authored
Hackily handle this with a begin block and return a default that matches current use.
-
- 22 May, 2013 1 commit
-
-
Mitch Tishmack authored
Instead of assuming that the Settings.gitlab['user'] home directory is: /home/git Obtain the default value from Etc and use that if not set in config.yml.
-
- 16 May, 2013 1 commit
-
-
Dmitry Medvinsky authored
“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
-
-
Dmitriy Zaporozhets authored
-
- 26 Apr, 2013 1 commit
-
-
Andrew8xx8 authored
-
- 24 Apr, 2013 1 commit
-
-
Andrew8xx8 authored
Conflicts: config/gitlab.yml.example config/initializers/1_settings.rb
-
- 28 Feb, 2013 1 commit
-
-
Andrew8xx8 authored
-
- 14 Feb, 2013 2 commits
-
-
Jaakko Kantojärvi authored
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.
-
Andrew8xx8 authored
-
- 11 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 07 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 31 Jan, 2013 1 commit
-
-
Mike Wyatt authored
-
- 20 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Jan, 2013 1 commit
-
-
Marin Jankovski authored
-
- 17 Jan, 2013 1 commit
-
-
Cyril authored
error is that ```enabled ||= true``` always evaluates to true. Change all initialization of bool settings to use the same syntax: ```setting = true if setting.nil?```
-
- 16 Jan, 2013 2 commits
-
-
Riyad Preukschas authored
-
Riyad Preukschas authored
-