primeminder VS bors-ng

When Twitch Prime was originally released one of the major issues was reminding people that their token was available. I built primeminder as a tool to remind people to renew their Twitch Prime subscription via email notifications: https://github.com/gravyboat/primeminder, the plan was to eventually advertise in the body of the emails once the user base was large enough.

The second was a remote job board like weworkremotely called remote-first. This was when weworkremotely was younger and I was pretty dissatisfied with the fact they didn't even support searching for jobs, it was just a messy list that was a pain to search so I thought I could do better to solve this.

Both projects failed.

You can further protect main branch by using a rollup approach (see Bors for an example) where the pre-merge tests are run against the combination of those PRs currently proposed for merging, which limits the possibility that two PRs look OK but together break something.

Completely independent implementations of the same underlying concept, one of which was written pretty much just for the rust project, and the other was written as a more general tool and service.

Merge commit (via bors) because I hate squash merges.

Maybe the author does not know that there's https://bors.tech which is a publicly available Bors instance. There's absolutely no operational cost involved except for the initial setup.

Or images. On pages like https://bors.tech and https://foodpartners.us the "bloat" is all images. The images are bigger than they were in the 1990's because they look better, even if you don't think they communicate more "information" people may still want them.

According to the README, it bisects. It doesn't matter much for me, though - the batches in our case were never big.

https://github.com/bors-ng/bors-ng/blob/master/README.md#how...

Sounds like they settled on the bors model of a batching merge queue. Gitlab's merge trains instead speculatively run all of the merges at once which gives more precise data at a higher cost and longer time, if your number of parallel runners is limited.