An error occurred fetching the project authors.
  1. 23 Sep, 2019 1 commit
  2. 10 Sep, 2019 1 commit
  3. 10 Jul, 2019 1 commit
  4. 10 Jun, 2019 1 commit
    • Luke Duncalfe's avatar
      Authorize access before serving project template · ba377e91
      Luke Duncalfe authored
      Previously, if a user was a guest member of a private project, they
      could access the merge request template as we were not checking
      permission-levels of the user.
      
      When a issue template is asked for, the user must have :read_issue for
      the project; or :read_merge_request when a merge request template is
      asked for.
      
      We also now rescue_from FileNotFoundError and handle as 404. This is
      because RepoTemplateFinder can raise a FileNotFoundError exception,
      which Rails previously handled as a 500.
      
      Handling these in a way that is consistent with
      ActiveRecord::RecordNotFound exceptions, within controllers that
      inherit from Projects::ApplicationController at least, and returning a
      404.
      
      https://gitlab.com/gitlab-org/gitlab-ce/issues/54943
      ba377e91
  5. 29 May, 2019 1 commit
  6. 25 May, 2019 1 commit
  7. 21 May, 2019 2 commits
  8. 20 May, 2019 1 commit
  9. 22 Jan, 2019 1 commit
  10. 03 Dec, 2018 1 commit
  11. 05 Oct, 2018 1 commit
  12. 20 Sep, 2018 1 commit
  13. 28 Aug, 2018 1 commit
  14. 24 Aug, 2018 1 commit
  15. 23 Jul, 2018 1 commit
  16. 12 Jun, 2018 1 commit
  17. 06 Apr, 2018 1 commit
    • James Ramsay's avatar
      Add new repository archive route · 07f517d4
      James Ramsay authored
      Repository archives are always named `<project>-<ref>-<sha>` even if
      the ref is a commit. A consequence of always including the sha even
      for tags is that packaging a release is more difficult because both
      the ref and sha must be known by the packager.
      
      - add `<project>/-/archive/<ref>/<filename>.<format>` route using the
      `-` separator to prevent namespace collisions. If the filename is
      `<project>-<ref>` or the ref is a sha, the sha will be omitted,
      otherwise the default filename will be used.
      - deprecate previous archive route `repository/<ref>/archive`
      07f517d4
  18. 31 Oct, 2017 1 commit
  19. 03 Aug, 2017 1 commit
  20. 27 Jul, 2017 1 commit
  21. 19 Jul, 2017 1 commit
  22. 28 Jun, 2017 1 commit
  23. 14 Jun, 2017 1 commit
  24. 02 Jun, 2017 1 commit
  25. 25 May, 2017 1 commit
    • Alexander Randa's avatar
      Implement web hooks logging · 330789c2
      Alexander Randa authored
      * implemented logging of project and system web hooks
      * implemented UI for user area (project hooks)
      * implemented UI for admin area (system hooks)
      * implemented retry of logged webhook
      * NOT imeplemented log remover
      330789c2
  26. 24 May, 2017 1 commit
  27. 19 May, 2017 1 commit
  28. 05 May, 2017 1 commit
  29. 28 Apr, 2017 1 commit
  30. 18 Apr, 2017 1 commit
  31. 06 Mar, 2017 1 commit
    • Eric Eastwood's avatar
      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
      e6fc0207
  32. 01 Mar, 2017 1 commit
  33. 03 Feb, 2017 1 commit
  34. 31 Jan, 2017 1 commit
    • 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
  35. 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
  36. 23 Nov, 2016 1 commit
  37. 11 Oct, 2016 1 commit
    • Sean McGivern's avatar
      Allow browsing branches that end with '.atom' · 1022456b
      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!
      1022456b
  38. 11 Aug, 2016 1 commit
  39. 02 Aug, 2016 1 commit