21–30 of 145 posts
* 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 files like README.md.
* pre { tab-size: 4 }
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.
If ZenHub supports making its features available to OSS projects without needing every contributor to install the extension, that's much more compelling, and also totally not obvious from their website.
(Yes, by which I am saying their website has not improved much given their massive funding)
I'd also love for commit messages to be parsed as markdown. I can't really think of a downside to it.
I'd be much more enthusiastic if there was some magical way for the local git command line to also support Markdown rendering/preview.
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…
Earlier quoted context omitted.
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 was the name I was trying to think of, thanks, but it seems like a thing everyone needs to opt into to make good use of (I think? in that it's a browser extension?). The idea I had is more along the lines of the CI badges, which don't require any action on the end-user's part. It's just an image inside a link, so it works in every browser already. If ZenHub supports making its features available to OSS project…
Yep! Which is why I gave up on trying to use it. I thought it would gain major traction given how useful it is - but I felt like the only person using it. So I eventually removed the extension.
>Not affiliated, used it, but without others using it it's largely...well.. useless. :)
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…
A github CI would be awesome! I imagine it would get very costly for them though. I love Travis-CI and the easy integration, but it's too expensive for my non-open source projects.
Anyway, if you want it today consider using our GitLab CI https://about.gitlab.com/gitlab-ci/ it is free if you bring your own runner.
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? 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…
I bet you could work on small polish issues like this for a lifetime and never finish. There's always something to improve.