An error occurred fetching the project authors.
- 31 Jan, 2017 6 commits
-
-
Kamil Trzcinski authored
1. PagesController is used to show all domains and general overview of Pages 2. PagesDomainsController is used to manage pages domains
-
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
-
Ritave authored
Fixes #24021
-
- 18 Jan, 2017 1 commit
-
-
Jose Ivan Vargas authored
-
- 11 Jan, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 03 Jan, 2017 1 commit
-
-
Jose Ivan Vargas authored
This controller is going to contain both the project members and groups options for the settings gear. Generated the route and modified the routing to point to the new members setting path
-
- 21 Dec, 2016 3 commits
-
-
Filipa Lacerda authored
Fix broken test Remove spinach tests for the builds tab
-
Filipa Lacerda authored
Remove unused file Fix commit link
-
Filipa Lacerda authored
Fix specs
-
- 19 Dec, 2016 4 commits
-
-
Kamil Trzcinski authored
- Add proper error handling, - Use flash[:alert] and flash[:notice], - Use `resource` instead of `resources`,
-
Fatih Acet authored
-
Z.J. van de Weg authored
[ci skip]
-
Kamil Trzcinski authored
``` Endpoint: /group/project/pipelines/id/stage.json?stage=name Call: stage_namespace_project_pipeline_path(pipeline.project.namespace, pipeline.project, pipeline, stage: stage.name) ```
-
- 17 Dec, 2016 1 commit
-
-
Luke "Jared" Bennett authored
-
- 16 Dec, 2016 3 commits
-
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
- 15 Dec, 2016 1 commit
-
-
Luke Bennett authored
Finished up autocomplete_sources action and added frontend to fetch data only when its needed Added wait_for_ajax to specs Fixed builds and improved the setup/destroy lifecycle Changed global namespace and DRYed up loading logic Added safety for accidentally loading data twice Removed destroy as its not necessary and is messing with click events from a blur race condition Created AutocompleteSourcesController and updated routes Fixed @undefined from tabbing before load ends Disable tabSelectsMatch until we have loaded data Review changes
-
- 30 Nov, 2016 1 commit
-
-
Filipa Lacerda authored
-
- 23 Nov, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 Nov, 2016 3 commits
-
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
- 09 Nov, 2016 1 commit
-
-
Toon Claes authored
It adds a button to the branches page that the user can use to delete all the branches that are already merged. This can be used to clean up all the branches that were forgotten to delete while merging MRs. Fixes #21076.
-
- 07 Nov, 2016 2 commits
-
-
tiagonbotelho authored
reactivates all tests and writes more tests for it
-
Dmitriy Zaporozhets authored
* split on multiple files * improve routing order Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 Oct, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 14 Oct, 2016 1 commit
-
-
Luke Bennett authored
-
- 13 Oct, 2016 1 commit
-
-
Sean McGivern authored
When reading conflicts: 1. Add a `type` field. `text` works as before, and has `sections`; `text-editor` is a file with ambiguous conflict markers that can only be resolved in an editor. 2. Add a `content_path` field pointing to a JSON representation of the file's content for a single file. 3. Hitting `content_path` returns a similar datastructure to the `file`, but without the `content_path` and `sections` fields, and with a `content` field containing the full contents of the file (with conflict markers). When writing conflicts: 1. Instead of `sections` being at the top level, they are now in a `files` array. This matches the read format better. 2. The `files` array contains file hashes, each of which must contain: a. `new_path` b. `old_path` c. EITHER `sections` (which works as before) or `content` (with the full content of the resolved file).
-
- 11 Oct, 2016 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Sean McGivern authored
We need to do two things to support this: 1. Simplify the regex capture in the routing for the CommitsController to not exclude the '.atom' suffix. That's a perfectly valid git branch name, so we shouldn't blow up if we get it. 2. Because Rails now can't automatically detect the request format, add some code to do so in `ExtractPath` when there is no path. This means that, given branches 'foo' and 'foo.atom', the Atom feed for the former is unroutable. To fix this: don't do that! Give the branches different names!
-
- 06 Oct, 2016 3 commits
-
-
James authored
-
Phil Hughes authored
-
Paco Guzman authored
-
- 05 Oct, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-