Skip to content
Snippets Groups Projects
  1. Apr 05, 2020
  2. Mar 30, 2020
  3. Mar 27, 2020
  4. Apr 05, 2020
    • Georges Racinet's avatar
      pull-force-topic: avoid divergence in overlapping pulls · 359d9bf9e090
      Georges Racinet authored
      As reported in heptapod#226, repeatedly importing the same
      changeset rewrites it several time, which is the very
      definition of content divergence.
      
      With these changes, we avoid re-pulling a changeset that's
      already present, yet obsolete. In the stacked PR use-case,
      the end result is that the second topic is orphan, but that's
      a much more frequent and easier to solve condition.
      
      We actually already had something for a similar case in the
      form of `non_obsolete_revs()`, but at the time the scenario of
      stacked PRs had been thought of only a posteriori, at the
      time of writing the docstring
      for the corresponding `test_already_obsolete()`. We could
      have thinked a bit more here.
      
      In truth `non_obsolete_revs()` is probably useless with our
      solution which is to take obsolete changesets into account in
      the initial assessment of the pull to be made, and that
      reflects with it not filtering anything in our existing tests.
      Since we are on the eve of a major release, we still keep it
      out of caution, only adding a direct test to restore coverage
      359d9bf9e090
  5. Mar 30, 2020
  6. Mar 27, 2020
  7. Mar 16, 2020
  8. Mar 26, 2020
  9. Mar 25, 2020
  10. Mar 18, 2020
  11. Mar 17, 2020
  12. Mar 16, 2020
  13. Mar 15, 2020
  14. Mar 14, 2020
    • Georges Racinet's avatar
      Extensions: activating 'share' · 49f988c0934d
      Georges Racinet authored
      It will notably be useful for all cases where the server
      needs to use a working directory, so that concurrency can
      be supported.
      49f988c0934d
    • Georges Racinet's avatar
      using the new gitlab_mirror hook · 79bbbafd2ddb
      Georges Racinet authored
      From now on, Heptapod will write directly into GitLab's Git
      repository.
      79bbbafd2ddb
    • Georges Racinet's avatar
      Merged heptapod-0-8 for new hg-git system · a2a5a534b6ab
      Georges Racinet authored
      The new hg-git rewrapping (that works directly on GitLab's
      Git repository) is available yet not in use in the heptapod-0-8
      branch.
      
      We will activate it in the default branch, targetting GitLab 12
      a2a5a534b6ab
    • Georges Racinet's avatar
      git: postponing post-receive after transaction is closed · 384a4df225f5
      Georges Racinet authored
      As already indicated in the former Heptapod fork of hg-git,
      at this point the changes are already visible, but the locks aren't
      released. This is enough to be relevant to whatever GitLab needs to do,
      while preventing another push to change things before our post-receive
      is queued.
      
      Nowadays this latter protection is rather theoretical: GitLab treatment
      is highly asynchronous anyway.
      384a4df225f5
    • Georges Racinet's avatar
      git: clarity refactors · c1d8a5e3e0ff
      Georges Racinet authored
      Renamed `topic_new_hg_sha()` into `analyze_vanished_topic`,
      which underlines that it works on a topic that is no more
      visible.
      
      Split out `analyze_vanished_refs()` from `compare_exportable`,
      to make the general articulation more visible.
      
      Gave more explicit namings to many variables.
      c1d8a5e3e0ff
    • Georges Racinet's avatar
      git: split generate_prune_changes() from compare_exportable() · 91e5a7ad866d
      Georges Racinet authored
      This makes it easier to unit-test and we take the opportunity
      to catch `RepoLookupError` in detection of previously closed
      branches.
      91e5a7ad866d
    • Georges Racinet's avatar
      git: honouring prune-previously-closed-branches=no · 0f1a020b7c06
      Georges Racinet authored
      we could have dropped this setting, but it was simpler to just
      make it work
      0f1a020b7c06
  15. Mar 13, 2020
  16. Mar 12, 2020
    • Georges Racinet's avatar
      gitlab hooks: stop returning None for no changes · 506e8eeacf44
      Georges Racinet authored
      This is more robust.
      
      It was originally intended as a way for callers to check
      the condition, but it makes something to check systematically
      (exception in string concatenation downstream if forgotten)
      and it's better if callers check before hand (worst case they
      will emit empty lines in the likes of `ui.status` if forgotten)
      506e8eeacf44
  17. Mar 13, 2020
  18. Mar 12, 2020
Loading