This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-28
Channels
- # aleph (16)
- # announcements (7)
- # asami (4)
- # aws (26)
- # babashka (26)
- # babashka-sci-dev (50)
- # beginners (118)
- # biff (7)
- # calva (15)
- # cider (6)
- # clj-kondo (8)
- # cljs-experience (3)
- # clojure (30)
- # clojure-austin (26)
- # clojure-europe (20)
- # clojure-france (2)
- # clojure-ireland (1)
- # clojure-nl (3)
- # clojure-norway (2)
- # clojure-spec (7)
- # clojure-uk (6)
- # clojurescript (12)
- # community-development (5)
- # conjure (1)
- # copenhagen-clojurians (3)
- # core-typed (71)
- # cursive (3)
- # datomic (1)
- # emacs (4)
- # fulcro (2)
- # helix (2)
- # introduce-yourself (3)
- # jobs (1)
- # london-clojurians (6)
- # lsp (122)
- # malli (2)
- # missionary (5)
- # overtone (14)
- # pathom (4)
- # polylith (1)
- # reagent (4)
- # reitit (1)
- # releases (1)
- # shadow-cljs (80)
- # testing (10)
- # tools-deps (6)
- # vim (3)
- # xtdb (19)
Magit specific, but can I get this error to be ignored when running magit-checkout-branch
? This is always thrown with any unstaged change, even when I'm creating a new branch from the current HEAD (which inherently can't conflict)
Cannot checkout when there are uncommitted changes
Is there a better way to do this? This is one of the last uses that I still have for git
CLI over magit; faster to run git checkout -b
than 2x magit-stash
+ magit-checkout-branch
.
Do you mean magit-branch-checkout
?
Either way, I don't get that error (with magit 3.3.0), even when I have tracked changes, so maybe it's on your end? :thinking_face:
Can you share your magit config and version?
(Btw aren't you running magit commands from the magit-status buffer?
Even if you had to do "2x magit-stash
+ magit-checkout-branch
" you'd only have to write z z b c <name of branch> z p
which is - probably- still easier to type than git checkout -b)