localslackirc VS dear-github

> Really? Just a git command, a button press on GitHub? So why don't they just do it? Why don't they apply the patches when people send the code in then?

Because the patch was bad.

> Something like a month later the guy just rewrote the patch without even engaging with me.

Do you think he'd have done that if the patch was good? Was his version completely identical to yours?

> Yeah, that made me feel like shit

At least it didn't introduce a new bug to every user… I'm sure collective feelings of the userbase were less harmed in this case.

> Sorry but maintainers don't have the moral superiority to demand free labor

But you have the moral superiority to demand free labour from maintainers, to review, improve, test your patch?

Look at this pull request for example: https://github.com/ltworf/localslackirc/pull/387

How could a thing like that be merged?

When asked to split it, he just proceeded to open tens of pull requests that were all based on the previous one, in a chain. And every commit contains thousands of lines of unrelated changes with what the description is.

Then he got upset.

plugging my IRC gateway https://github.com/ltworf/localslackirc

I find that using slack from IRC, and having the option to deprive some people/channels to notify me is very helpful to reduce the amount of distractions.

I could never understand why people insist on using requests rather than the stdlib (which works just fine).

When async became a thing, I remember hitting some bug in aiohttp so I wrote myself a tiny (just doing the bit I needed) HTTP async client, which I figured was easier than wrestling aiohttp into compliance.

These days aiohttp is quite nice for async, and for sync I just use the stdlib.

My async client, if it can be of interest https://github.com/ltworf/localslackirc/blob/master/slackcli...

I normally use [localslackirc](https://github.com/ltworf/localslackirc) to use slack.

I can grep through the logs if I need to find something. That's really really fast compared to their search on the website.

I also get other advantages such as not automatically being forced to see all the reaction GIFs and being able to silence notifications from certain users that abuse them.

https://github.com/ltworf/localslackirc/ if you are interested.

GitHub makes this unnecessarily worse by refusing to let you disable Pull Requests like one can disable the other social features (Wiki etc) of a repository: https://github.com/dear-github/dear-github/issues/84

The workaround is to use GH Actions to auto-close PRs: https://github.com/marketplace/actions/repo-lockdown

There is no way to disable pull requests on GitHub. Only some weird work-arounds for auto-closing them with Actions

> don't let people waste their time creating issues in the first place

But then you don't get to use issues to track things that you personally care about. It would be nice if there were a way to enable issue creation by the repo owner / maintainers, but disallow it for the public at large. Especially now that "discussions" are a thing, which gives a place for people to comment without implicitly requesting work from the maintainer.

Apparently this is sort of possible[1] by setting `blank_issues_enabled: false`, so that you can only create issues from the Project page.

[1]: https://github.com/dear-github/dear-github/issues/293#issuec...

last I've seen the Oauth permissions for the Heroku Dashboard given by Github are excessive and include write access to all public repos - as read-only is not an option if I recall correctly, see https://github.com/dear-github/dear-github/issues/113#issuec...

Newer integrations like Github Apps are more granular and can restrict the scope , also ssh deploy keys are an option for other purposes, but specifically the tokens issued for the Heroku Dashboard can write to the public repos of a user or org.

Without active triage and maintenance, such a list would quickly become useless. Let's look at just one example that's not even for an open source project: https://github.com/dear-github/dear-github/issues/214

Found these ways to submit bug to github: https://support.github.com/contact/feedback https://support.github.com/request https://github.com/isaacs/github#if-you-have-an-issue-or-feature-request-for-github https://github.com/dear-github/dear-github [email protected] Submitting tickets using an enterprise account

You're right, likely the OP thought PRs were included in settings where you can disable issues or wikis

Discussion: https://github.com/dear-github/dear-github/issues/84