Seven steps » git http://trevoke.net/blog Martial arts and technology, $DEITY what a mix! Tue, 11 May 2010 20:52:46 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Github’s customer service: bad review http://trevoke.net/blog/2010/03/12/githubs-customer-service-bad-review/ http://trevoke.net/blog/2010/03/12/githubs-customer-service-bad-review/#comments Fri, 12 Mar 2010 14:39:28 +0000 Trevoke http://trevoke.net/blog/?p=224 I will readily admit that I don’t know all that much about Github or Git for that matter. I use them, they’re handy, and that’s where it stops. I read about a git feature called “smart HTTP”, which would allow to communicate both ways with git (push and pull) with HTTP or HTTPS. So, I asked Github about it – it would be nice for them to have this feature, because I currently can’t push to Github from work. Here’s how the exchange went.
(this first message is from memory, as I used the web interface, so I don’t have a copy of it)
Me:
Hi, I just read about this: http://progit.org/2010/03/04/smart-http.html and I would like to know when Github plans on implementing this, because it would be very useful.
_______
From: Tekkub (Support staff)
Subject: [Contact] Upgrading git to support smart HTTP ?

You do know that Scott (the guy who wrote Pro Git) works for us, right? We’re well
aware of smart http…
_______
I tried to make light of the condescending tone and sent the following reply:
Me:
Nope.. Had no idea.
So when will it be implemented? ;)
_______
From: Tekkub (Support staff)
Subject: [Contact] Upgrading git to support smart HTTP ?

It will be implemented when it is…
_______

That’s when I just gave up. I don’t know if whoever handles the messages is paid or not, but I’m pretty sure Github pays its employees by now. I’m using a free account, so they wouldn’t lose anything by me leaving them, and they do provide a great service.
Am I just being picky when I expect the support staff to be polite? I say this as someone who has worked as support staff for over three years: no. The support staff SHOULD, nay, MUST be polite. I don’t care how flat your company hierarchy is, I don’t care how young or forward-thinking the company is, and I especially don’t care if your target audience is Asperger’s syndrome-suffering programmers who laugh at Star Trek jokes and read slash fiction. You’re the support, you’re polite. Especially over a medium like text, where you can’t easily place a slap on the shoulder, a grin and a wink.

This has left a bad taste in my mouth.

]]> http://trevoke.net/blog/2010/03/12/githubs-customer-service-bad-review/feed/ 5 Git : moving a remote branch http://trevoke.net/blog/2009/12/29/git-moving-a-remote-branch/ http://trevoke.net/blog/2009/12/29/git-moving-a-remote-branch/#comments Tue, 29 Dec 2009 22:08:43 +0000 Trevoke http://trevoke.net/blog/?p=204 One can’t actually move a remote branch, but you can copy a branch and delete a branch, so…

Copy oldbranch in repo to newbranch.

git push {repo} {oldbranch}:heads/{newbranch}

Ex: git push origin foobranch:barbranch
renames foobranch to barbranch

Remove a remote branch: it’s all about the colon:

git push <remote_repo> :heads/<branch>

Example: git push origin :heads/some-branch removes some-branch from the remote repo (apparently git push origin :some-branch works as well).

This works for removing a tag as well: git push origin :sometag

]]> http://trevoke.net/blog/2009/12/29/git-moving-a-remote-branch/feed/ 0