dear-github
repo-lockdown
dear-github | repo-lockdown | |
---|---|---|
8 | 4 | |
5,151 | 132 | |
0.0% | - | |
0.0 | 6.5 | |
over 3 years ago | 6 months ago | |
JavaScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dear-github
-
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
repo-lockdown
-
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
-
Nimalyzer, a static code analyzer for Nim (early alpha).
And thank you for the link. I agree, automation is needed here. :) I'm using a different GitHub action: https://github.com/dessant/repo-lockdown
-
Ask HN: How did you recover from burnout?
Something that really helps me uncouple programming from burnout is having a strictly-non-collaborative personal project in a language/ecosystem I intentionally avoid in the professional world. It's still open source Free Software but I don't ever want a pull request or even a bug report because then it becomes work and means the codebase is no longer a 1:1 representation of my own brain-space/goals/style.
Not that I have received any of those things, but I have steeled myself to be ready to turn it down if it ever does. The social pressure is real, and Github doesn't even let you disable pull requests so I had to configure a bot to automatically be an asshole for me: https://github.com/dessant/repo-lockdown
Here's the message I configured in my `.github/lockdown.yaml`:
```comment: Please accept my apologies for your wasted effort in closing this pull request, but I am not prepared to accept changes on this project at this time, if ever. This is a personal project for my personal website that I'm happy to share, but I want the code to be all mine. I would not be able to mentally connect with my codebase as well if it were a reflection of anyone but myself, and accepting others' code complicates the copyright situation regardless of the software license used. Please e-mail me with any bug reports :)```
- Repo Lockdown is a GitHub Action that immediately closes and locks issues and pull requests.
What are some alternatives?
csgo-osx-linux - Counter-Strike: Global Offensive
listen-to-wikipedia - Live, generative music and visualisation from Wikipedia edits. Forked from http://listen.hatnote.com/ with some customisation.
ctf-collab - Collaborative programming environment inside GitHub Actions – like Google Docs for hacking
issue-stats-card - Analyse a github repo's issues then generates a table of stats for quick info.
linux - Linux kernel source tree
backup-github-repo - Backup all the issues and pull requests of a Github repo, including the comments, events, and labels, as JSON and as HTML
gatsby-plugin-s3 - Deploy your gatsby site to a S3 bucket.
missue - A Toolkit helps you to management your TODO based on GitHub Issues.
uBlock - uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
label-actions - 🤖 GitHub Action that performs certain tasks when issues, pull requests or discussions are labeled or unlabeled
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
amazing-github-template - 🚀 Useful README.md, LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, GitHub Issues, Pull Requests and Actions templates to jumpstart your projects.