Skip to content
Snippets Groups Projects
  1. Jan 10, 2020
  2. Jan 07, 2020
  3. Jan 05, 2020
  4. Dec 21, 2019
    • Georges Racinet's avatar
      git_sync: stop using SSH · 2d639205
      Georges Racinet authored
      This is part of heptapod#144: now that we're firing the
      pre-receive hook ourselves, we don't need to go over SSH at all.
      
      This also means that we don't need the `repositories-root`
      confiuration item anymore.
      2d639205
  5. Dec 19, 2019
  6. Dec 24, 2019
  7. Dec 18, 2019
  8. Dec 19, 2019
  9. Dec 16, 2019
  10. Dec 15, 2019
  11. Dec 14, 2019
  12. Dec 12, 2019
    • Georges Racinet's avatar
      pull-force-topic: two corner cases · aa5e2184
      Georges Racinet authored
      found these by redoing a pull-force-topic after a first one
      (with an incomplete strip leading to the error)
      aa5e2184
    • Georges Racinet's avatar
      Introducing a pull-force-topic command · cf947479
      Georges Racinet authored
      This is meant to import Pull Requests from external
      systems, such as Bitbucket.
      
      We don't provide a way to also change the branch in this
      first implementation (users can do it afterwards if they want to).
      But if it turns out we get lots of MRs wrongly targetted
      because of this, we'll do it.
      
      The implementation is a lower version of doing
      hg `incoming --bundle`, followed by `hg log` on the
      bundle to know the contained changesets, and then
      `hg unbundle` and `hg topic TOPIC`
      
      Being lower level than the CLI, we can do the whole
      in one single transaction, which will be important
      for Heptapod (single inner Git push)
      
      We decided to stay quite close to the CLI surface though,
      hence we still need to link the bundle file on the filesystem,
      and reopen it aftewards. We could have instead cherry-picked
      from the `exchange.pull`, but that would have been awkward.
      
      If we turn out to have problems with real life cases with
      phases or obsmarkers, we could cherry-pick from  `exchange.pull`
      instead, but that will be more complicated.
      cf947479
  13. Dec 13, 2019
  14. Dec 14, 2019
  15. Dec 13, 2019
    • Georges Racinet's avatar
      ci: allowing failures against Mercurial default · 873adb41
      Georges Racinet authored
      in our cases, failures depend whether other extensions,
      such as evolve or hg-git are themselves ready for Mercurial
      default.
      
      Currently we do have a test in a topic that's broken because
      evolve 9.2.1 is not compatible with Mercurial default.
      We will of course change the build to use evolve default, but
      it's not guaranteed to work, and even so, that may break later on.
      
      We don't want to stall our development for this.
      873adb41
Loading