Live data from Hacker News

Things I would build if I worked at GitHub

kevin.is

41–50 of 145 posts

Re: Things I would build if I worked at GitHub

#41
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?

Re: Things I would build if I worked at GitHub

#43
post #33

Wiki search is #1 on my wish list for Github. I see others talking about cloning the wiki repo locally and searching it but for big projects this would be the equivalent of downloading something like the Python docs and searching them. It could be done but it would be a massive pain in the ass. I have written most of the documentation for the project I contribute to the most and I organized the wiki like a two level…

If you use Chrome you have an option here: https://chrome.google.com/webstore/detail/github-wiki-search...

Re: Things I would build if I worked at GitHub

#45

My biggest pet-peeve about GitHub is its issue tracker system. It's great for one-off issues or tracking a pull-request, but beyond that its design is super unwieldy. Such a missed opportunity to crush JIRA, et. al.

What do you miss the most or find cumbersome or unusable?

- Issues that span multiple projects

- Searching all issues for an organization

- Voting on issues (not just :+1:)

- Public issues for private repos

- Attaching files (repros, necessary files, etc.)

- Dependencies/links

- Priority (you can label priority but not sort by it)

- Metrics of any kind

Re: Things I would build if I worked at GitHub

#46
A better way to browse forks.

If today you see that a major repository has a fork with a lot of commits, you cannot know without looking through THEM ALL if they are just typo fixes or if the fork is really changing/improving things over the main repo.

Re: Things I would build if I worked at GitHub

#47
post #32
post #21

Just see the top requested features: https://github.com/isaacs/github/issues?q=is%3Aissue+is%3Aop... * Change the target branch of a pull request pull-requests * Delete / remove an issue completely. * Gist comments and mentions don't trigger notifications * Add HTTPS support to Github Pages * Add ability to follow organizations like a user * Insert automatically generated table of contents TOC on rendered markdown fi…

> Add HTTPS support to Github Pages This is technically already available, though not officially documented anywhere [1]. Example [2] [1] https://github.com/isaacs/github/issues/156#issuecomment-377... [2] https://beltex.github.io

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

Re: Things I would build if I worked at GitHub

#49

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…

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?

Bugfixes are not feature enhancements.

Also this makes you sound like a pleasant person to work with.....a real go getter.

Post reply on HN