An error occurred fetching the project authors.
  1. 13 Mar, 2019 2 commits
  2. 12 Mar, 2019 2 commits
  3. 06 Mar, 2019 3 commits
  4. 05 Mar, 2019 1 commit
  5. 01 Mar, 2019 2 commits
  6. 27 Feb, 2019 2 commits
    • Jacopo's avatar
      Add project http fetch statistics API · 1b7ade7d
      Jacopo authored
      The API get projects/:id/traffic/fetches allows user with write
      access to the repository to get the number of clones for the
      last 30 days.
      1b7ade7d
    • Jacopo's avatar
      Add project http fetch statistics API · 5ae9a44a
      Jacopo authored
      The API get projects/:id/traffic/fetches allows user with write
      access to the repository to get the number of clones for the
      last 30 days.
      5ae9a44a
  7. 26 Feb, 2019 4 commits
  8. 25 Feb, 2019 5 commits
  9. 20 Feb, 2019 2 commits
  10. 18 Feb, 2019 1 commit
  11. 11 Feb, 2019 1 commit
  12. 08 Feb, 2019 2 commits
  13. 06 Feb, 2019 4 commits
  14. 04 Feb, 2019 2 commits
  15. 01 Feb, 2019 1 commit
  16. 31 Jan, 2019 3 commits
  17. 29 Jan, 2019 2 commits
    • Adrian Moisey's avatar
      Add GitLab Pages predefined variables · 88d1ec62
      Adrian Moisey authored
      88d1ec62
    • Andreas Brandl's avatar
      Flush InternalId records after import · fede3a0b
      Andreas Brandl authored
      After the import has finished, we flush (delete) the InternalId records
      related to the project at hand. This means we're starting over with
      tracking correct internal id values, a new record will be created
      automatically when the next internal id is generated.
      
      The GitHub importer assigns iid values by using supplied values from
      GitHub. We skip tracking internal id values during the import in favor
      of higher concurrency. Deleting any InternalId records after the import
      has finished is an extra measure to guarantee consistency.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54270.
      fede3a0b
  18. 28 Jan, 2019 1 commit