Things I would build if I worked at GitHub • Hacker News Board

Re: Things I would build if I worked at GitHub

#131

Post by masklinn » Thu, Aug 06, 2015, 10:02 AM UTC

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.

ZenHub is a chrome-only browser extension, that sounds all kinds of terrible.

Re: Things I would build if I worked at GitHub

#132

Post by mellett68 » Thu, Aug 06, 2015, 10:03 AM UTC

tsuresh wrote: post #12

GitHub wiki is a repo and can be cloned locally. Searching through a local files is trivial.

I'd argue that's still a bit of a pain compared to a fulltext search in the browser. I can already search the rest of the repo and issues that way, so why not the wiki?

Good tip though.

Re: Things I would build if I worked at GitHub

#133

Post by masklinn » Thu, Aug 06, 2015, 10:05 AM UTC

> The suggested alternative is to "Subscribe" to an issue for updates, which is what I've started doing to issues that I want to show my support for. My support, however, isn't visible to anyone else.

Though following the resolution of an issue usually means I'd like for it to be resolved, the converse isn't true: I've hit thousands of issues over the years but most of the time I've been able to work around them and haven't hit it since, resolving the issue would be nice for people coming after me, but I don't really care to be spammed by its status updates.

So yes, "subscribe" could count as a +1, but no "subscribe" should not be the only way to "+1" an issue.

Re: Things I would build if I worked at GitHub

#134

Post by johnbellone » Thu, Aug 06, 2015, 10:31 AM UTC

danielsamuels wrote: post #40

I've gotta say, I strongly disagree with this: > GitHub already has a great code search At some point in the last year or so Github rolled out a new search engine which drastically reduced it's usefulness. Any moderately complex search query now has all of the modifiers and key bits stripped out making your search results unnecessarily cluttered and somewhat useless. I consider it to be one of the worst parts of the…

GitHub has horrible search.

Re: Things I would build if I worked at GitHub

#135

Post by kolev » Thu, Aug 06, 2015, 12:11 PM UTC

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…

All these are nice, but are not must-haves as they can be built outside of GitHub. The show-stopper for me is granular permissions - coming from the Gitolite [0] world, where I can permission even branches and do all kinds of checks and balances on the server, GitHub is a joke for a not-so-large enterprise! Another thing is the Wiki - why pages are based on Git and the Wiki is not?!

[0] http://gitolite.com/

Re: Things I would build if I worked at GitHub

#136

Post by zeckalpha » Thu, Aug 06, 2015, 12:53 PM UTC

richmarr wrote: post #118

zeckalpha wrote: post #101

Earlier quoted context omitted.

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.

Too bad you can't open a pull request to GitHub.com, no?

Re: Things I would build if I worked at GitHub

#137

Post by kirushik » Thu, Aug 06, 2015, 4:01 PM UTC

tracker1 wrote: post #53

holic wrote: post #47

Earlier quoted context omitted.

While that's true, I think the discussion in that issue has gone more towards HTTPS support for custom domains.

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.

Re: Things I would build if I worked at GitHub

#138

Post by Jemaclus » Thu, Aug 06, 2015, 4:10 PM UTC

The only thing I really, really want is paginated diffs for pull requests. C'mon. If I have 300 files, don't show me the first 15 and then say "well, this is too big, you'll just have to imagine what the rest of the diff looks like." Does Google return the first page and then say "the rest of the internet isn't available to you because we don't want to paginate things"? No, of course not. Just freaking paginate long diffs.

Gah.

Re: Things I would build if I worked at GitHub

#139

Post by bronson » Thu, Aug 06, 2015, 5:33 PM UTC

teddyh wrote: post #121

bronson wrote: post #117

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.

If you want anything less centralized, then why are you using Github, a centralized interface to and storage of a previously inherently de -centralized system, git? Github is for people who accept centralization.

That's not true. Why do you think github promotes forking and pull requests?

Some centralization is necessary, true, but you seem to be confusing GitHub with Google Code and SourceForge.

Re: Things I would build if I worked at GitHub

#140

Post by h43k3r » Fri, Aug 07, 2015, 12:39 PM UTC

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…

Exactly my thoughts.

After exploring Visual Studio Online (its free for 5 users), I am still not able to digest why there isn't a build and deploy system in GitHub.

There were great demos at Microsoft's BUILD15 for Automated Build and Release Management which demonstrates these features.