I always wished GitHub had a chat room per repo. Fully integrated with github features, like mentions, issues, pull requests. Maybe even hubot builtin.
gitter?
Things I would build if I worked at GitHub
81–90 of 145 posts
Re: Things I would build if I worked at GitHub
#82Earlier quoted context omitted.
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 :(
What appeals to you about mailing lists? If it's reporting issues, discussion solutions, and reviewing patches, there are Issues and Pull Requests. If it's for general discussions about the "future of the project" or bigger-picture topics, I'd use Discourse. It's a really nice way to organize discussions that are one step removed from code-related issues. If it's for things where you need quick or real time feedback,…
> If it's for general discussions about the "future of the project" or bigger-picture topics, I'd use Discourse. It's a really nice way to organize discussions that are one step removed from code-related issues.
This is what is appealing and Github offering a builtin-to-github solution for it, with linking to Github accounts, autoformatting etc (like in issues) and so on. There is so much potential.
Re: Things I would build if I worked at GitHub
#83git hubs worst problem: FIXED WIDTH CODE READING code is read way more often than written. and on github website all you can do is read it. why the viewports don't take up the entire screen width i will never understand.
It is long lines which damage readability, and that is the fault of the gonk who wrote the code. If anything, GH's fixed-width design encourages shorter lines and so improves readability.
Re: Things I would build if I worked at GitHub
#84It's very common, at least on my team, to create pull requests for the wrong target branch. I don't see why GitHub doesn't allow you to fix it before any comments are posted. This would save some useful time.
Re: Things I would build if I worked at GitHub
#85Wiki 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...
Awesome, already used this twice. Thanks!
Re: Things I would build if I worked at GitHub
#86Earlier quoted context omitted.
>This is GitHub after all; why don't we build stuff ourselves instead of waiting for a centralized closed-source company to decide they care about our features? Why would I build something for a centralized closed-source company?
Because then the only thing you're relying on the centralized closed-source company for is actual git hosting. This is a boring problem that dozens of other services solve well, and thousands of other services (like S3) solve poorly in a pinch. If you can migrate the interesting part of GitHub -- issue tracking, PRs, wikis, etc. -- to another provider, and GitHub just holds your data, then you're no longer locked in.…
You could build the features for GitLab. We'll roll them out on GitLab.com that you can use for free. We can import repo's and issues already and are working on PR's and wiki's.
Re: Things I would build if I worked at GitHub
#87Earlier quoted context omitted.
It's actually very surprising how little visible improvement GitHub has had in the past few years. What are they working on?
Marketing by the looks of it. I have to say I like what Gitlab is doing these days much more than GitHub.
Glad to hear that, our company and community tries to keep shipping!
Re: Things I would build if I worked at GitHub
#88Earlier quoted context omitted.
> 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.
I wonder if letsencrypt will allow that to become practical?
Re: Things I would build if I worked at GitHub
#89These 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…
GitHub CI and artifacts are great ideas. Owning the chain of Dev - test - deploy would be a superb move, one worth paying for!
Re: Things I would build if I worked at GitHub
#90> These are great, but they're bugfixes.
I agree with every you said but that first sentence. How are these bugs? They are features that never existed.