FEfemiagbabiaka·Nov 30, 2025
It's not directly possible, no, but with branch protection rules and this Github action it is trivial to set up:
https://github.com/dessant/repo-lockdown
In Zigbook Is Plagiarizing the Zigtools Playgrounddessant
repo-lockdown
JavaScript2020–2025
dessant / repo-lockdown
repo-lockdown
GitHub Action that immediately closes and locks issues and pull requests
2Distinct people
3Mentions
0Explicit recommenders
145GitHub stars
What to know before exploring
What it is
GitHub Action that immediately closes and locks issues and pull requests
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year3 dated mentions
Observed mentions: 2020-07-05 18:51:49 UTC to 2025-11-30 15:12:49 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesSomething 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 clos
Read the rest
ing 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 :)```
I wish Github let me disable Pull Requests on my repos for this reason. You can disable Issues, Wikis, and lots of other features, but not Pull Requests. For certain projects I end up checking a `.github/lockdown.yml` into my repo and using https://github.com/dessant/repo-lockdown
In Linus Torvalds: 'I Do No Coding Any More'