This instance will be upgraded to Heptapod 0.21.0rc2 on 2021-04-16 at 14:00 UTC+2 (a few minutes of down time)

  1. 04 Sep, 2020 3 commits
  2. 24 Aug, 2020 1 commit
  3. 04 Aug, 2020 3 commits
  4. 31 Jul, 2020 2 commits
  5. 30 Jul, 2020 3 commits
  6. 27 Jul, 2020 1 commit
    • Georges Racinet's avatar
      Merging heads on branch default · e0ebc7343459
      Georges Racinet authored
      Actually that second head was on mirror.octobus.net only
      (found by CI experiments for heptapod/heptapod which install
      this from mirror.o.n), but it's enough of a pain to merge it
      explicitely.
      
      Of course diff with `p1()` should be empty
      e0ebc7343459
  7. 24 Jul, 2020 3 commits
  8. 16 Jul, 2020 2 commits
  9. 11 Jul, 2020 1 commit
    • Georges Racinet's avatar
      GitLab pre-receive: pass new vcs='hg' parameter · 9a913324753c
      Georges Racinet authored
      Related to heptapod#295: this parameter will make it
      possible to differentiate between calls to the `/allowed` internal
      API endpoint for pre-receive checks (common among supported VCSes)
      and for Git client SSH operation.
      
      Since it'll make the pre-receive call use the `HgAccess` class
      instead of the previously used `GitAccess`, we need now also to
      pass the corresponding Mercurial wire protocol command name for
      pushes.
      9a913324753c
  10. 08 Jul, 2020 3 commits
  11. 29 Jun, 2020 4 commits
  12. 28 Jun, 2020 2 commits
    • Georges Racinet's avatar
      subrepos: forbid any pull of subrepos on the server side · 75d393740150
      Georges Racinet authored
      See heptapod#311
      
      Subrepos are not needed to update a file, or to perform a
      merge. In a later version, we could simply neutralize the
      pull, but then we'd have to make sure that the commit logic
      is consistent (that's why commits are forbidden separately,
      too).
      
      In current Heptapod, the use of updates is always within
      shares used for server side operations and mergeability
      assessment. This change will prevent
      projects using subrepos to trigger hundreds of pulls that will
      take too much time, and create resource problems (maybe
      banning risks even) for hazardeous success anyway.
      75d393740150
    • Georges Racinet's avatar
      subrepos: a hook to forbid server-side commits · 89aaf7286fe7
      Georges Racinet authored
      See heptapod#311 for rationale
      89aaf7286fe7
  13. 29 Jun, 2020 1 commit
    • Georges Racinet's avatar
      git for subrepos: more robust parsing of .hgsub · eec9087800f7
      Georges Racinet authored
      We'd still have a long way to go for proper subrepositories
      support in Heptapod. With this change, at least, we won't get
      errors because a `.hgsub` file has a `subpaths` section.
      
      More precisely, we're using the same config parser as Mercurial
      does for this file.
      eec9087800f7
  14. 26 Jun, 2020 2 commits
  15. 24 Jun, 2020 4 commits
  16. 18 Jun, 2020 3 commits
  17. 17 Jun, 2020 2 commits
    • Georges Racinet's avatar
      branch: branchmap to gitlab branch conversion utilities · 9b95ea74c395
      Georges Racinet authored
      The provided `branchmap_branch_from_gitlab_branch()` is not
      equivalent to the `GitHandler.git_branch_for_branchmap_branch()`
      method, whose purpose is also to gate invalid new content, and
      needs a `ui` object for user feedback.
      
      When we drop the hg-git conversion, we'll do such validations
      separately.
      9b95ea74c395
    • Georges Racinet's avatar
      heptapod.gitlab.branch, split out of hgext3rd.heptapod.git · 311cd85da3bc
      Georges Racinet authored
      The pure bytes-string manipulation functions will need to
      be cleanly reused from elsewhere, and notably in HGitaly.
      
      This is also an opportunity to normalize and explain the
      terminology.
      311cd85da3bc