BigW Consortium Gitlab

  1. 19 Jan, 2017 2 commits
  2. 18 Jan, 2017 2 commits
    • Add some API endpoints for time tracking. · 0f3c9355
      Ruben Davila authored
      New endpoints are:
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_estimate"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_time_estimate"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/add_spent_time"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_spent_time"
      
      GET  :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_stats"
    • Respond with validation errors in commit status API · 9ce8aa31
      Grzegorz Bizon authored
      If validation errors are present, include validation errors in the
      commit status API payload, instead of depending on state machine errors
      caused by invalid record.
  3. 16 Jan, 2017 1 commit
  4. 15 Jan, 2017 2 commits
  5. 12 Jan, 2017 3 commits
    • API: Implement project issues iid param with IssuesFinder and add tests · 7ef1c640
      David Eisner authored
      - Use IssuesFinder for the /issues API resouce
      - Tests for iid filter in project issues API resource
      - Tests for No Milestone filter in issues API resources
        The "No Milestone" case was not previously tested, and the `/issues`
        resource did not support the the `milestone` parameter.
      - Return issues where all labels match from the issues and project issues
        API resources, like the group issues resource already does. See
        https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6825#note_17474533Signed-off-by: 's avatarRémy Coutable <remy@rymai.me>
    • Adding 'IssueFinder' for 'projects' API endpoint · 5c253116
      Panagiotis Atmatzidis authored
      Current filtering for "/projects/:id/issues" endpoint
      returns no results for "No Milestone" query.
      
      This PR introduces fix by copying filtering from "/groups/:id/issues"
      which works as expected.
    • Add support for PlantUML diagrams in Asciidoc. · f986b4c4
      Horacio Sanson authored
      This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a
      PlantUML diagram all we need is to include a plantuml block like:
      
      ```
      [plantuml, id="myDiagram", width="100px", height="100px"]
      --
      bob -> alice : ping
      alice -> bob : pong
      --
      ```
      
      The plantuml block is substituted by an HTML img element with *src* pointing to
      an external PlantUML server.
      
      This MR also add a PlantUML integration section to the Administrator -> Settings
      page to configure the PlantUML rendering service and to enable/disable it.
      
      Closes: #17603
  6. 11 Jan, 2017 1 commit
  7. 09 Jan, 2017 1 commit
  8. 08 Jan, 2017 1 commit
    • Record and show last used date of SSH Keys · b6df93a5
      Vincent Wong authored
      Addresses: Issue #13810
      
      1. Adds a last_used_at attribute to the Key table/model
      2. Update a key's last_used_at whenever it gets used
      3. Display how long ago an ssh key was last used
  9. 05 Jan, 2017 1 commit
  10. 04 Jan, 2017 3 commits
  11. 03 Jan, 2017 5 commits
  12. 29 Dec, 2016 1 commit
  13. 28 Dec, 2016 1 commit
  14. 23 Dec, 2016 1 commit
  15. 22 Dec, 2016 1 commit
  16. 21 Dec, 2016 4 commits
  17. 20 Dec, 2016 6 commits
  18. 19 Dec, 2016 2 commits
  19. 18 Dec, 2016 1 commit
  20. 16 Dec, 2016 1 commit
    • Accept environment variables from the `pre-receive` script. · f82d549d
      Timothy Andrew authored
      1. Starting version 2.11, git changed the way the pre-receive flow works.
      
        - Previously, the new potential objects would be added to the main repo. If the
          pre-receive passes, the new objects stay in the repo but are linked up. If
          the pre-receive fails, the new objects stay orphaned in the repo, and are
          cleaned up during the next `git gc`.
      
        - In 2.11, the new potential objects are added to a temporary "alternate object
          directory", that git creates for this purpose. If the pre-receive passes, the
          objects from the alternate object directory are migrated to the main repo. If
          the pre-receive fails the alternate object directory is simply deleted.
      
      2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the
         `/allowed` endpoint, which calls out directly to git to perform
         various checks. These direct calls to git do _not_ have the necessary
         environment variables set which allow access to the "alternate object
         directory" (explained above). Therefore these calls to git are not able to
         access any of the new potential objects to be added during this push.
      
      3. We fix this by accepting the relevant environment variables
         (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the
         `/allowed` endpoint, and then include these environment variables while
         calling out to git.
      
      4. This commit includes (whitelisted) these environment variables while making
         the "force push" check. A `Gitlab::Git::RevList` module is extracted to
         prevent `ForcePush` from being littered with these checks.