An error occurred fetching the project authors.
  1. 06 Feb, 2017 1 commit
  2. 03 Feb, 2017 4 commits
  3. 02 Feb, 2017 1 commit
    • Sean McGivern's avatar
      Check public snippets for spam · c63194ce
      Sean McGivern authored
      Apply the same spam checks to public snippets (either personal snippets
      that are public, or public snippets on public projects) as to issues on
      public projects.
      c63194ce
  4. 31 Jan, 2017 7 commits
    • Timothy Andrew's avatar
      Fix 500 error while navigating to the `pages_domains` 'show' page. · 86f4767d
      Timothy Andrew authored
      ==================
      = Implementation =
      ==================
      
      1. The path of the page is of the form 'group/project/pages/domains/<domain_name>'
      2. Rails looks at `params[:id]` (which should be the domain name), and finds the
         relevant model record.
      3. Given a domain like `foo.bar`, Rails sets `params[:id]` to `foo` (should be
         `foo.bar`), and sets `params[:format]` to `bar`
      4. This commit fixes the issue by adding a route constraint, so that
         `params[:id]` is set to the entire `foo.bar` domain name.
      
      =========
      = Tests =
      =========
      
      1. Add controller specs for the `PagesDomainController`. These are
         slightly orthogonal to this bug fix (they don't fail when this bug is
         present), but should be present nonetheless.
      2. Add routing specs that catch this bug (by asserting that the `id`
         param is passed as expected when it contains a domain name).
      3. Modify the 'RESTful project resources' routing spec shared example to
         accomodate controllers where the controller path (such as
         `pages/domains`) is different from the controller name (such as
         `pages_domains`).
      86f4767d
    • Kamil Trzcinski's avatar
      Split PagesController into PagesController and PagesDomainsController · 7f12cb0e
      Kamil Trzcinski authored
      1. PagesController is used to show all domains and general overview of Pages
      2. PagesDomainsController is used to manage pages domains
      7f12cb0e
    • Kamil Trzcinski's avatar
      Fix the remove_pages · e5e2e7b7
      Kamil Trzcinski authored
      e5e2e7b7
    • Kamil Trzcinski's avatar
      13b6bad1
    • Kamil Trzcinski's avatar
      Initial work on GitLab Pages update · 5f7257c2
      Kamil Trzcinski authored
      5f7257c2
    • Kamil Trzcinski's avatar
      Add GitLab Pages · 120f9aba
      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
      120f9aba
    • Ritave's avatar
      Abillity to promote project labels to group labels · 5d871dcc
      Ritave authored
      Fixes #24021
      5d871dcc
  5. 18 Jan, 2017 1 commit
  6. 11 Jan, 2017 1 commit
  7. 03 Jan, 2017 1 commit
  8. 21 Dec, 2016 3 commits
  9. 19 Dec, 2016 4 commits
  10. 17 Dec, 2016 1 commit
  11. 16 Dec, 2016 3 commits
  12. 15 Dec, 2016 1 commit
    • Luke Bennett's avatar
      Changed autocomplete_sources into an action that returns a single 'at' type of sources at a time · 1356e40f
      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
      1356e40f
  13. 30 Nov, 2016 1 commit
  14. 23 Nov, 2016 1 commit
  15. 17 Nov, 2016 3 commits
  16. 09 Nov, 2016 1 commit
    • Toon Claes's avatar
      Add button to delete all merged branches · 1afab9eb
      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.
      1afab9eb
  17. 07 Nov, 2016 2 commits
  18. 17 Oct, 2016 2 commits
  19. 14 Oct, 2016 1 commit
  20. 13 Oct, 2016 1 commit
    • Sean McGivern's avatar
      Allow setting content for resolutions · 3f71c43e
      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).
      3f71c43e