SaaSHub helps you find the best software and product alternatives Learn more →
Dear-github Alternatives
Similar projects and alternatives to dear-github
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Avalonia
Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
ctf-collab
Collaborative programming environment inside GitHub Actions – like Google Docs for hacking
dear-github reviews and mentions
-
Mental Health in Open Source
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
-
When people assume open source also means open to contribution
There is no way to disable pull requests on GitHub. Only some weird work-arounds for auto-closing them with Actions
-
Just Say No
> 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...
-
On April 7, 2022, a threat actor obtained access to a Heroku database
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.
-
No, "Open Source" does not mean "Includes Free Support"
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
-
Bug in get page viewes API?
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
-
GitHub Actions update: Helping maintainers combat bad actors
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
-
A note from our sponsor - SaaSHub
www.saashub.com | 27 Apr 2024
Stats
Sponsored