listen-to-wikipedia
repo-lockdown
| listen-to-wikipedia | repo-lockdown | |
|---|---|---|
| 1 | 4 | |
| 1 | 132 | |
| - | - | |
| 0.0 | 6.5 | |
| over 3 years ago | 5 months ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 or later | 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.
listen-to-wikipedia
-
Listen to Wikipedia
Great project. I made a fork of this recently that starts in full-screen mode: http://skhg.github.io/listen-to-wikipedia/?fullscreen for ambient sound on our TV
Repo at https://github.com/skhg/listen-to-wikipedia
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?
wiki - Wikipedia Interface for Node.js
issue-stats-card - Analyse a github repo's issues then generates a table of stats for quick info.
useful-forks.github.io - Improving GitHub's Forks list discoverability through automatic filtering. The project offers an online tool and a Chrome extension.
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
Fomantic-UI - Fomantic-UI is the official community fork of Semantic-UI
missue - A Toolkit helps you to management your TODO based on GitHub Issues.
pull - 🤖 Keep your forks up-to-date via automated PRs
label-actions - 🤖 GitHub Action that performs certain tasks when issues, pull requests or discussions are labeled or unlabeled
firedragon-browser - A Floorp fork with custom branding 🐉 (mirrored from GitLab)
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.