Rip's Domain

Disable the github issue tracker. Use pull requests instead?

Posted in Opensource by rip747 on January 7, 2013

Why is it that github even has an issue tracker? Doesn’t it make more sense to have bug reports and enhancement requests submitted through pull requests?

Think about it for a moment:

How many times has someone filed a bug report giving you little or unclear information. Now you have to waste your time trying to contact the person to get more specific information. This could have been totally avoided if the person would have written a failing test demonstrating the bug in the first place.

How many enhancement requests have you’ve gotten that, though seemed like a good idea, required an enormous amount of effort or was something that a single person needed. Why didn’t the requester take the time to code the enhancement so as to not consume the time of the project author(s)?

As an experiment I’m going to do this with the new project I’ve started. I’m hoping that by removing the issue tracker it will encourage more people to step out of their comfort zone and participate.

Tagged with: , , ,

GIT clone over HTTP: who knew?

Posted in Git, TechSupport by rip747 on September 12, 2008

Quick note for others and so I don’t forget.

If you’re behind a proxy (like I am) and try to do a git-clone using the git:// protocol, surely it will fail if you’re firewall is restrictive. The beautiful thing is, you can use http:// protocol instead to get around this restriction.

So for instance, let’s say we want to clone a copy of yubnub from github. In the cygwin command line, you would normally do:

git clone git://github.com/jcnetdev/yubnub.git

However that will fail. Instead do:

git clone http://github.com/jcnetdev/yubnub.git

The only other gotcha is that you might need to setup your proxy in your environment. To do this, simply do:

export http_proxy=http://<username>:<password>@<proxy_ip>:<proxy_port>

where:

username = your network username (someuser)
password = your network password (somepassword)
proxy_ip = the ip address of your proxy server (192.168.1.1)
proxy_port = the port number for the proxy (80)

the full string would look like this:

export http_proxy=http://someuser:somepassword@192.168.1.1:80

Tagged with: