An error occurred fetching the project authors.
- 04 Jul, 2017 1 commit
-
-
Paweł Chojnacki authored
-
- 20 Jun, 2017 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 19 Jun, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 07 Jun, 2017 1 commit
-
-
Robin Bobbitt authored
-
- 02 Jun, 2017 2 commits
-
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
-
- 01 Jun, 2017 1 commit
-
-
Douwe Maan authored
-
- 30 May, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 22 May, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 07 May, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 27 Apr, 2017 1 commit
-
-
Chris Wilson authored
GitLab uses the import_project method in GitLab Shell, This method uses a timeout for the operation, hardcoded to 800 seconds. With this MR the timeout is now configurable in the gitlab_shell settings.
-
- 19 Apr, 2017 1 commit
-
-
Jakub Jirutka authored
Hard-coding location of configuration files is very bad practice. This patch applies the same approach as currently used for gitlab_shell_secret file.
-
- 11 Apr, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 06 Apr, 2017 3 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 03 Apr, 2017 1 commit
-
-
Ahmad Sherif authored
Closes gitaly#166
-
- 30 Mar, 2017 1 commit
-
-
Rémy Coutable authored
Use full path for moving directories when changing namespace path See merge request !2078
-
- 29 Mar, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 21 Mar, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 14 Mar, 2017 1 commit
-
-
Stan Hu authored
Note that the old migrations depend on 1_settings.rb, so we can't quite remove those completely.
-
- 10 Mar, 2017 2 commits
-
-
Jacob Vosmaer authored
-
Sean McGivern authored
If there is an existing gitlab.yml file with snippets explicitly disabled, they won't be enabled with this change.
-
- 08 Mar, 2017 1 commit
-
-
Nick Thomas authored
-
- 04 Mar, 2017 1 commit
-
-
medied authored
-
- 03 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- 02 Mar, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 01 Mar, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 28 Feb, 2017 1 commit
-
-
Jon Keys authored
-
- 15 Feb, 2017 2 commits
-
-
Annabel Dunstone Gray authored
-
Annabel Dunstone Gray authored
-
- 01 Feb, 2017 1 commit
-
-
Mike Greiling authored
-
- 31 Jan, 2017 5 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- The pages are created when build artifacts for `pages` job are uploaded - Pages serve the content under: http://group.pages.domain.com/project - Pages can be used to serve the group page, special project named as host: group.pages.domain.com - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB) - The public/ is extracted from artifacts and content is served as static pages - Pages asynchronous worker use `dd` to limit the unpacked tar size - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml - Pages are part of backups - Pages notify the deployment status using Commit Status API - Pages use a new sidekiq queue: pages - Pages use a separate nginx config which needs to be explicitly added
-
- 21 Dec, 2016 1 commit
-
-
Alex authored
-
- 17 Dec, 2016 1 commit
-
-
Kamil Trzcinski authored
-