a lot of times ill work on projects on the way to work and then i would like to do a push when i get into the office in the morning, assuming every thing is working :). However ssh to non-local machines is blocked at work. there are ways around it using special vpn profiles and the like, but this looks a lot easier.
The big advantage comes when the URL is public somehow - like with git submodules. The http/https URL works for both read-only and read-write users unlike git:// or git@ URL's.
The disadvantage is that http/https can only be pushed to by users who have git 1.7.
1: Github crew, can we get a way to use our API token or some other revokable token as a password for HTTPS repo operations? I appreciate that anything involving “revokable tokens” is really hard to make a decent UI for, but it just feels bad keeping that in my .netrc file.
Isn't this exactly how their regular SSH access works? If you don't want an SSH key to work anymore, just remove it from GitHub.
9 comments
[ 3.7 ms ] story [ 28.3 ms ] threadAll I can see is being on a foreign computer. When on a foreign computer I generally don't even have git so why bother.
The disadvantage is that http/https can only be pushed to by users who have git 1.7.
Isn't this exactly how their regular SSH access works? If you don't want an SSH key to work anymore, just remove it from GitHub.
* sometimes ssh is blocked
* HTTPS can be used to pull from public projects anonymously, or without configuration; the same URL can then be used later to push.
* HTTPS also works just fine without any configuration or password storage, it just nags you for a username and password if it needs it
I think in general, as well as this particular case, it would be better to do
One doesn't always want to merge from the remote branch.While I'm ok with that, it'd be nice to have a <noscript> section saying so, rather than just having large chunks of your content missing.