This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-18
Channels
- # announcements (1)
- # aws (13)
- # beginners (55)
- # calva (8)
- # cider (73)
- # cljs-dev (96)
- # clojure (119)
- # clojure-europe (4)
- # clojure-italy (41)
- # clojure-nl (14)
- # clojure-uk (6)
- # clojurescript (90)
- # cursive (14)
- # data-science (1)
- # datomic (20)
- # dirac (1)
- # emacs (32)
- # figwheel-main (11)
- # fulcro (81)
- # hoplon (2)
- # jobs (1)
- # lein-figwheel (2)
- # luminus (1)
- # lumo (19)
- # nyc (3)
- # off-topic (60)
- # other-languages (1)
- # pedestal (5)
- # quil (1)
- # re-frame (3)
- # reagent (3)
- # reitit (5)
- # remote-jobs (1)
- # ring-swagger (2)
- # shadow-cljs (43)
- # sql (15)
- # tools-deps (20)
- # vim (21)
- # yada (6)
Interesting... Thinking I'll attempt the path of adding an SSH key to the CI. If too painful, will try the clojure
script hacking.
@kenny You can also play with gitconfig and for instance switch between ssh and https without code changes
# [url " "]
# insteadOf = :
[url "[email protected]:"]
insteadOf =
part of my ~/.gitconfig
@jeroenvandijk But this won't let tools-deps support https auth, correct?
My guess is that you can even achieve that https://git-scm.com/docs/gitcredentials
i did only the opposite as the https auth for github is limited
we're using circleci and they even have a feature to add an ssh key of another user (over a deploy key) to the project automatically
@alexmiller what do you think about gitlibs making clones read only so that they aren't accidentally modified by user error?
you mean the working tree I presume
seems reasonable
readonly directory means you cannot add or remove to it. modifying an existing file is still fair play
I assumed that's what we were talking about
the dirs under ~/.gitlibs/libs are sha-pegged and shouldn't change
does changing those properties affect whether it looks like the correct working tree to git?
I guess I'm asking if file attributes affect the sha, but looks like no