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

111–120 of 145 posts

Re: Things I would build if I worked at GitHub

#111

Post by iancarroll »

simonw wrote: post #110
simonw wrote: post #109

The biggest thing I want from GitHub is the ability to search commits. GitHub are pretty good at search (their issue search is fantastic, and their code search is decent enough) - but the data I most want to search are the commit messages in my repo. I understand this will be a huge amount of data (they must have hundreds of millions if not billions of commits by now). I'd be perfectly happy if this was only availabl…

Oh, and while we're talking pony requests... I'd dearly love to be able to use gists within the scope of an organization. It would be fantastic to be able to share code snippets that were only visible to other organization members (and searchable and so on).

I know this isn't exactly what you want, but GitHub Enterprise comes with Gist.

Re: Things I would build if I worked at GitHub

#114

Post by krakensden »

scrollaway wrote: post #57
felixgallo wrote: post #17

These are great, but they're bugfixes. You'd finish them in the first few months. Then what are you going to do? Stare at an aquarium all day? Here's what I would build if I worked at github: * Github CI - simple CI for every language, integrating with: * Github Artifacts - repository for versioned deployable build packages (binaries, tar.gz files, ios builds, android builds...), integrating with: * Github Deploy - d…

Of all the things I wish Github had, a mailing list service would be really amazing, and the kind of thing that wouldn't be done in the first few months. Sourceforge offers atrocious mailman-based email, larger foss projects on github suffer :(

Librelist is pretty decent.

Re: Things I would build if I worked at GitHub

#115

Post by Eiriksmal »

felixgallo wrote: post #17

These are great, but they're bugfixes. You'd finish them in the first few months. Then what are you going to do? Stare at an aquarium all day? Here's what I would build if I worked at github: * Github CI - simple CI for every language, integrating with: * Github Artifacts - repository for versioned deployable build packages (binaries, tar.gz files, ios builds, android builds...), integrating with: * Github Deploy - d…

Great minds... I was talking about this the other day with the other engineers at work, after learning about GitHub's most recent monstrous funding round. It seems like CI/a deployment service and something that competes in the crowded PaaS field is the next logical step.

AWS enables us to do some pretty slick things, but OpsWorks is a giant bag of suck that frequently finds a way to drain my time troubleshooting why something crazy or random has happened on the production server--behaviors I never saw in my previous role running a bare-metal LAMP stack for 4 years. A tighter integration between our GitHub repo and a testing/build server... Swoon.

Re: Things I would build if I worked at GitHub

#116

Post by dvanduzer »

scrollaway wrote: post #102
zeckalpha wrote: post #101

Earlier quoted context omitted.

So that's the one blocker? Creating an issue via email?

No, the blocker is setting up mailing lists with a forum-like interface (cf. discourse), but integrated to github (uses the github account) and without actually having to do the setup. Also, without polluting issues.

Good project-specific labels to GH issues solves the "polluting" problem. The label/tag system is nicely flexible.

It sounds like what you really want is nested threads and top quoting and/or interstitial quote/response features?

(Arguably what you really need is commonly called a conference.)

Re: Things I would build if I worked at GitHub

#117

Post by bronson »

How about making pull requests less centralized? Right now, if I file a PR, only the project admins or I can modify/rebase it. I'd like to give other (non-admin) collaborators permission to work on it too.

Or, maybe it could use a forking model? Let anyone fork their own PR from mine, make those forks prominently visible in my base PR, and make it easy for me to merge their edits back in.

Re: Things I would build if I worked at GitHub

#118

Post by richmarr »

zeckalpha wrote: post #101
scrollaway wrote: post #99

Earlier quoted context omitted.

Because then users can't simply send an email to create a new topic to talk about...

So that's the one blocker? Creating an issue via email?

You can do that via API, so it's pretty trivial to set up using an integrator like Zapier or tray.io.

Re: Things I would build if I worked at GitHub

#119

Post by reustle »

Nadya wrote: post #13
geofft wrote: post #5

It seems like some of these (perhaps all of them other than fixing the "+1" problem) can be done via API clients instead of via GitHub itself implementing it. A third-party website can do wiki searches. A separate service can send you email notifications, and you can turn off built-in emails. Even the +1 thing might be solvable with a bot that edits each bug report to add a clickable +1 badge (a la the CI build-passi…

The +1 thing is solved by ZenHub - which I'm amazed they've been unable to gather a large amount of traction! https://www.zenhub.io/ Not affiliated, used it, but without others using it it's largely...well.. useless. :) E: Hmm... seems it has become $5/mo to use. I remember it being free. Wonder when that happened? E2: >ZenHub is free for the open source community. Oh.

Not only $5/mo, but $5/mo/user which is surprisingly expensive.

Re: Things I would build if I worked at GitHub

#120

Post by pbiggar »

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.

Post reply on HN