Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things I would build if I worked at GitHub

kevin.is

Post reply on HN
Print view View original

141–145 of 145 posts

Re: Things I would build if I worked at GitHub

#141

Post by rkuykendall-com »

bqe wrote: post #41
kzhahou wrote: post #23

They'll need another $100 million to get these done! (Yes, by which I am saying their website has not improved much given their massive funding)

It's actually very surprising how little visible improvement GitHub has had in the past few years. What are they working on?

https://github.com/blog

Lots of things. Github ships features like crazy. Lots of the features I use every single day were only released in the last few months. On a scale of years, all of their desktop clients, which are a huge experience improvement for new users.

Re: Things I would build if I worked at GitHub

#142

Post by kranzky »

pbiggar wrote: post #120
kranzky wrote: post #91

Things I would build: * Push conflicted branches so developers in a distributed team can work together to resolve conflicts. * A git-powered version of Rake, which runs only those tests that need to be run based on the git history since the last run. * A tool to identify what code changes caused a particular test to fail, based on the above. * Language syntax detection for smarter diffs, improving the display when bl…

> * A git-powered version of Rake, which runs only those tests that need to be run based on the git history since the last run. I think you mean "magic". That is, this is not possible :) Not that I wouldn't like it to be.

Well, it is kind-of possible for Ruby/Rails. I half-built such a system once. Here's what you do:

* Gather coverage information when running tests or compiling assets.

* Use that to generate Rakefiles for running tests / compiling assets that have dependencies on the source files they would touch.

* Run the tests once, recording information about the git status of each dependency.

* When the git status of a file changes (i.e. you've just fetched some changes), mark the dependency as dirty

Even better, it you're gathering coverage data and know the test status for each commit, then not only can you show the commit that broke the build, you can show the particular part of the diff that broke the build.

Here's a guy who was trying to do some of this: https://github.com/Genki-S/ttnt

Re: Things I would build if I worked at GitHub

#143

Post by qmr »

sytse wrote: post #26

Great list, we're working on making something that makes +1's less noisey. If you want the possibility to contribute to the tools you use daily consider using our GitLab. It is open source and more than 800 people have contributed already.

Why is there no IPv6 support?

Re: Things I would build if I worked at GitHub

#144

Post by sytse »

qmr wrote: post #143
sytse wrote: post #26

Great list, we're working on making something that makes +1's less noisey. If you want the possibility to contribute to the tools you use daily consider using our GitLab. It is open source and more than 800 people have contributed already.

Why is there no IPv6 support?

I think GitLab supports it https://gitlab.com/gitlab-org/omnibus-gitlab/issues/412 but we have not had the time to set it up for GitLab.com yet. We'll be moving our infrastructure to Azure soon so it is not a priority for us now.

Re: Things I would build if I worked at GitHub

#145

Post by holic »

kirushik wrote: post #137
tracker1 wrote: post #53

Earlier quoted context omitted.

You could always use CloudFlare directly for that... I would presume that their underlying connection to Github is very close and reliable in terms of risk for MITM.

Even better, you could CNAME your custom domain into the *.github.io domain, which is protected by a wildcard https. So you traffic between CloudFlare and GitHub will also be secured.

Last I checked, this doesn't actually work with the way *.github.io is set up.
Post reply on HN