Read about our upcoming Code of Conduct on this issue

  1. 31 Jan, 2017 2 commits
    • Kamil Trzcinski's avatar
      Add GitLab Pages · bc5e3a4463d6
      Kamil Trzcinski authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under:
      - Pages can be used to serve the group page, special project named as host:
      - 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's avatar
      Abillity to promote project labels to group labels · 38d9affd8770
      Ritave authored
      Fixes #24021
  2. 18 Jan, 2017 1 commit
  3. 11 Jan, 2017 1 commit
  4. 03 Jan, 2017 1 commit
  5. 21 Dec, 2016 3 commits
  6. 19 Dec, 2016 4 commits
  7. 17 Dec, 2016 1 commit
  8. 16 Dec, 2016 3 commits
  9. 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 · 6c095ed273f7
      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
  10. 30 Nov, 2016 1 commit
  11. 23 Nov, 2016 1 commit
  12. 17 Nov, 2016 3 commits
  13. 09 Nov, 2016 1 commit
    • Toon Claes's avatar
      Add button to delete all merged branches · f20b6c5a8c7a
      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.
  14. 07 Nov, 2016 2 commits
  15. 17 Oct, 2016 2 commits
  16. 14 Oct, 2016 1 commit
  17. 13 Oct, 2016 1 commit
    • Sean McGivern's avatar
      Allow setting content for resolutions · 0483c1e6acbc
      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).
  18. 11 Oct, 2016 2 commits
    • Douglas Barbosa Alexandre's avatar
    • Sean McGivern's avatar
      Allow browsing branches that end with '.atom' · e5e22b8cf6fc
      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!
  19. 06 Oct, 2016 3 commits
  20. 05 Oct, 2016 1 commit