Hacker News new | ask | show | jobs
by eddythompson80 1097 days ago
It’s not that hard to setup. It’s a built-in feature in something like gitea. Or you can write a `git push` cron task or a server hook in git to keep the 2 in sync. GitHub is full of mirror repos. You can also disable issues, discussions, wiki, and pull requests if you don’t want to deal with that.
2 comments
retrocryptid 1097 days ago
That's what I'm doing now. It's what I don't want to do. I want the public repo to autopush PRs to my private repo so I don't have to poll it.

[LOL. A previous edit autocorrected "autopush" to "autopsy." Or maybe it was a Freudian slip on my part.]

link
eddythompson80 1097 days ago
You can trigger a GitHub action on any PR and run any arbitrary code you want.
link
retrocryptid 1097 days ago
Again. I DON'T want to run a script in a container on github's infrastructure.
link
eddythompson80 1097 days ago
If you’re polling, you can use GitHub APIs. They are pretty well documented. If you want a turn-key solution, use gitea. Depending on how flexible you need it, gitea might cover your scenarios. But you can have actions in gitea as well that automate polling GitHub APIs for issues or comments or pull requests etc.
link
uvatbc 1097 days ago
GitHub self hosted runners might address this concern.
link
oefrha 1097 days ago
> You can also disable … pull requests

That is the one thing you can’t disable on GitHub unless something changed recently. Very annoying for mirrors where development happens elsewhere.

link
TillE 1097 days ago
Make a README.md which clearly states this at the top, and a CONTRIBUTING.md. After that, it's just not your problem if someone opens a PR.
link
duskwuff 1097 days ago
There are a couple of other options, although I'll agree that none of them are ideal:

1) You can set up Github Actions to automatically close pull requests: https://github.com/marketplace/actions/close-pull-request

2) You can use "interaction limits" (in repository settings, under "moderation options") to limit repository interactions to collaborators. This can only be set for 6 months at a time, though, so you'll need to reactivate it periodically.

3) You can archive the project and unarchive it temporarily when making changes, disabling all activity on the fork.

link