Skip to content
Snippets Groups Projects
  1. Nov 22, 2021
  2. Nov 21, 2021
  3. Nov 22, 2021
  4. Jun 22, 2021
  5. Nov 05, 2021
  6. Nov 04, 2021
  7. Jul 06, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      push: output when non-pushable commits exist · 5b271ae3
      Dan Villiom Podlaski Christiansen authored
      This is an area where we have no choice but diverging from stock
      Mercurial, as Git does not allow anonymous heads. We can only push
      something that has either a bookmark or a tag.
      
      In order to lessen confusion for users, we output a message inspired
      by Mercurial's (ignoring %d secret commits) — which serves a similar
      purpose.
      5b271ae3
  8. Nov 03, 2021
  9. Jul 09, 2021
  10. Feb 05, 2021
  11. Oct 31, 2021
  12. Jul 09, 2021
  13. Aug 01, 2021
  14. Oct 22, 2021
  15. Jul 06, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      clone: do not activate a bookmark when cloning e.g. a tag · 74e72004
      Dan Villiom Podlaski Christiansen authored
      This makes it so that we only activate a bookmark on clone iff either:
      
      * -r/--rev was not specified and the remote HEAD points to a branch, or
      * the first -r/--rev specifies a bookmark
      74e72004
    • Dan Villiom Podlaski Christiansen's avatar
      push: abort with an error when no bookmarks or tags exist · 78cbae27
      Dan Villiom Podlaski Christiansen authored
      Previously, we would simply invent a master bookmark when this
      occurred, but in the specific case where the remote is empty. I
      believe that's actually unhelpful in the long run: Should a user not
      know about bookmarks, the first push will succeed, and subsequent
      pushes then not do anything. How did that bookmark get there?
      
      Instead, we should trigger a hard error for this case; that way, we'll
      hopefully cause the user to take a step back and find out how the
      command really works.
      78cbae27
  16. Feb 05, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      pull: do not invent or imply a "default" when none exists · 1c9ac8cf
      Dan Villiom Podlaski Christiansen authored
      As far as I can tell, this was previously used to "detect" an initial
      clone. Unfortunately, that logic is incorrect: like Mercurial, hg-git
      should consider pulling into an empty repository distinct from
      cloning.
      
      As an apparent aside, it also kind-of-sort-of handled the case where
      you pulled from a local Git repository into a location that happened
      to be default.
      
      To fix this, we do two things:
      
      1) Expand relative local paths before comparing them to other paths.
      2) Detect clone from the source of the default `default` path.
      
      The end result is:
      
      1) You can pull from e.g. `../repo` to update remotes, with an
         equivalent path specified in the configuration
      2) Pulls from entirely foreign remotes are no longer saved.
      3) We always activate the desired bookmarks on clone.
      
      Although the two changes might seem unrelated, their effect is
      combined, and either alone would break the tests.
      1c9ac8cf
  17. Jul 06, 2021
  18. May 31, 2021
  19. Jul 06, 2021
  20. Jun 24, 2021
  21. Jul 31, 2021
  22. Aug 01, 2021
  23. Jul 06, 2021
Loading