BigW Consortium Gitlab

  1. 06 Apr, 2017 1 commit
  2. 05 Apr, 2017 2 commits
  3. 31 Mar, 2017 3 commits
  4. 27 Mar, 2017 1 commit
  5. 23 Mar, 2017 3 commits
  6. 07 Mar, 2017 2 commits
  7. 06 Mar, 2017 2 commits
    • Use native unicode emojis · e6fc0207
      Eric Eastwood authored
       - gl_emoji for falling back to image/css-sprite when the browser
         doesn't support an emoji
       - Markdown rendering (Banzai filter)
       - Autocomplete
       - Award emoji menu
          - Perceived perf
          - Immediate response because we now build client-side
       - Update `digests.json` generation in gemojione rake task to be more
         useful and  include `unicodeVersion`
      
      MR: !9437
      
      See issues
      
       - #26371
       - #27250
       - #22474
  8. 02 Mar, 2017 1 commit
  9. 01 Mar, 2017 2 commits
    • Update occurrences of MWBS to MWPS · a0101ebf
      James Lopez authored
       Rename column in the database
       Rename fields related to import/export feature
       Rename API endpoints
       Rename documentation links
       Rename the rest of occurrences in the code
       Replace the images that contain the words "build succeeds" and docs referencing to them
       Make sure pipeline is green and nothing is missing.
      
      updated doc images
      
      renamed only_allow_merge_if_build_succeeds in projects and fixed references
      
      more updates
      
      fix some spec failures
      
      fix rubocop offences
      
      fix v3 api spec
      
      fix MR  specs
      
      fixed issues with partials
      
      fix MR spec
      
      fix alignment
      
      add missing v3 to v4 doc
      
      wip - refactor v3 endpoints
      
      fix specs
      
      fix a few typos
      
      fix project specs
      
      copy entities fully to V3
      
      fix  entity error
      
      more fixes
      
      fix failing specs
      
      fixed missing entities in V3 API
      
      remove comment
      
      updated code based on feedback
      
      typo
      
      fix spec
  10. 09 Feb, 2017 1 commit
  11. 06 Feb, 2017 3 commits
  12. 03 Feb, 2017 4 commits
  13. 02 Feb, 2017 1 commit
    • 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.
  14. 31 Jan, 2017 7 commits
    • 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`).
    • 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
    • Fix the remove_pages · e5e2e7b7
      Kamil Trzcinski authored
    • Initial work on GitLab Pages update · 5f7257c2
      Kamil Trzcinski authored
    • 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
    • Abillity to promote project labels to group labels · 5d871dcc
      Ritave authored
      Fixes #24021
  15. 18 Jan, 2017 1 commit
  16. 11 Jan, 2017 1 commit
  17. 03 Jan, 2017 1 commit
  18. 21 Dec, 2016 3 commits
  19. 19 Dec, 2016 1 commit
    • Improve sources · 34295036
      Kamil Trzcinski authored
      - Add proper error handling,
      - Use flash[:alert] and flash[:notice],
      - Use `resource` instead of `resources`,