1. 08 Jan, 2019 3 commits
  2. 02 Jan, 2019 1 commit
  3. 24 Dec, 2018 1 commit
  4. 21 Dec, 2018 1 commit
  5. 19 Dec, 2018 1 commit
  6. 18 Dec, 2018 3 commits
  7. 14 Dec, 2018 1 commit
  8. 13 Dec, 2018 1 commit
  9. 11 Dec, 2018 3 commits
  10. 07 Dec, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Allow public forks to be deduplicated · 896c0bdb
      Zeger-Jan van de Weg authored
      When a project is forked, the new repository used to be a deep copy of everything
      stored on disk by leveraging `git clone`. This works well, and makes isolation
      between repository easy. However, the clone is at the start 100% the same as the
      origin repository. And in the case of the objects in the object directory, this
      is almost always going to be a lot of duplication.
      Object Pools are a way to create a third repository that essentially only exists
      for its 'objects' subdirectory. This third repository's object directory will be
      set as alternate location for objects. This means that in the case an object is
      missing in the local repository, git will look in another location. This other
      location is the object pool repository.
      When Git performs garbage collection, it's smart enough to check the
      alternate location. When objects are duplicated, it will allow git to
      throw one copy away. This copy is on the local repository, where to pool
      remains as is.
      These pools have an origin location, which for now will always be a
      repository that itself is not a fork. When the root of a fork network is
      forked by a user, the fork still clones the full repository. Async, the
      pool repository will be created.
      Either one of these processes can be done earlier than the other. To
      handle this race condition, the Join ObjectPool operation is
      idempotent. Given its idempotent, we can schedule it twice, with the
      same effect.
      To accommodate the holding of state two migrations have been added.
      1. Added a state column to the pool_repositories column. This column is
      managed by the state machine, allowing for hooks on transitions.
      2. pool_repositories now has a source_project_id. This column in
      convenient to have for multiple reasons: it has a unique index allowing
      the database to handle race conditions when creating a new record. Also,
      it's nice to know who the host is. As that's a short link to the fork
      networks root.
      Object pools are only available for public project, which use hashed
      storage and when forking from the root of the fork network. (That is,
      the project being forked from itself isn't a fork)
      In this commit message I use both ObjectPool and Pool repositories,
      which are alike, but different from each other. ObjectPool refers to
      whatever is on the disk stored and managed by Gitaly. PoolRepository is
      the record in the database.
  11. 06 Dec, 2018 1 commit
    • Luke Bennett's avatar
      Document the "Abuse reports" feature · d3b14e9d
      Luke Bennett authored
      Add documentation for both admins (/user/admin_area/abuse_reports.md)
      and non-admins (/user/abuse_reports.md) to help them use
      the abuse reports feature
  12. 05 Dec, 2018 1 commit
  13. 30 Nov, 2018 1 commit
  14. 29 Nov, 2018 1 commit
  15. 27 Nov, 2018 1 commit
  16. 23 Nov, 2018 4 commits
  17. 21 Nov, 2018 1 commit
  18. 20 Nov, 2018 1 commit
  19. 16 Nov, 2018 2 commits
  20. 15 Nov, 2018 1 commit
  21. 14 Nov, 2018 1 commit
  22. 13 Nov, 2018 3 commits
  23. 12 Nov, 2018 1 commit
  24. 09 Nov, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Symlinked hooks aren't executed · ec6363d6
      Zeger-Jan van de Weg authored
      This recently changed on the Gitaly side, but now spotted this in the
      docs for the next release. Updated to be more precise, and to signal
      users should not want control over this specific hook location.
  25. 08 Nov, 2018 1 commit
  26. 07 Nov, 2018 3 commits