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

there's no such thing

readonly directory means you cannot add or remove to it. modifying an existing file is still fair play

you'd have to ensure that every file was r/o too

I assumed that's what we were talking about

I'll lodge a JIRA

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?

huh?

I guess I'm asking if file attributes affect the sha, but looks like no

Some do, like +x