Anders Brujordet
Anders Brujordet
This should also solve #18
You don't actually need the username, only the token. The differences is that on Github.com you don't need credentials to clone a a public repository over https, on GHE you...
Good point @Hi-Fi, added a line about it now.
I'm out and about so I had to resolve the conflicts in the browser, but should be fine as there was just minor stuff.
Alright, I just tested this again, to make sure. ``` $ git clone https://our.github.com/org/repo.git Cloning into 'repo'... Username for 'https://our.github.com': ^C $ git clone https://${GITHUB_TOKEN}@our.github.com/org/repo.git Cloning into 'repo'... remote: Enumerating...
Will do 👍
Tried to fix through the web ui, will have to get some time later on a proper machine.
@jeffa17 hi, it was actually my intention that this should only be a single token. Bypassing your own company's rate limit sounds like a good way to meet HR. But...
How are you generating the content for these clients? Do you have an identical structure for jobs or have you found a way of parameterising this? Ref #149
Interesting, could you please provide the output of 'echo $PS1' and 'locale'? This looks a bit like issues I saw when locale was set to 'C.UTF-8'