Skip to content
Snippets Groups Projects
  1. Jun 18, 2021
  2. May 12, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      phases: avoid accidentally marking a divergent bookmark as public · 4fb7c538
      Dan Villiom Podlaski Christiansen authored
      This essentially makes our behaviour match the documentation, which
      states that ``git.public`` refers to “a list of Git branches”. It
      didn't: it actually referred to a list of Mercurial changesets that we
      would publish on push.
      
      Previously, this would lead to a rather nonsensical situation:
      
      * The remote ``stable`` points to commit A
      * The local, corresponding ``stable`` bookmark points to commit B
      * ``git.public`` is configured to list ``stable``
      * The user performs a pull.
      
      Whatever you'd expect to happen in that case, it mostly likely
      _wouldn't_ be for B to be published, which was what happened.
      
      Please note that this change breaks backwards compatibility;
      previously, having ``git.public`` point to e.g. ``default/master``
      would cause that to be published. But that was always undocumented.
      4fb7c538
  3. Jun 18, 2021
  4. Jun 11, 2020
  5. Jun 22, 2021
  6. Jun 17, 2021
  7. Jun 16, 2021
  8. Jun 15, 2021
  9. Jun 16, 2021
  10. Jun 18, 2021
  11. May 08, 2021
  12. Jun 18, 2021
  13. Jun 02, 2021
  14. Jun 01, 2021
  15. May 31, 2021
  16. Sep 15, 2020
  17. Jun 13, 2021
  18. Jun 01, 2021
  19. May 19, 2021
  20. May 28, 2021
  21. May 22, 2021
  22. May 03, 2021
Loading