On 8/13/2025 2:43 AM, Michael Niedermayer wrote:
HiOn Tue, Aug 12, 2025 at 11:22:44PM +0200, Jean-Baptiste Kempf wrote:On Tue, 12 Aug 2025, at 17:59, Kacper Michajlow wrote:Because of course there is homer-bot... I think everyone seen marge-bot too https://github.com/smarkets/marge-bot (also GitLab specific)Be careful, those are 2 very different bots. Marge bot, is a bot to avoid the fight for all the MR to be rebased before merging them. You assign to Marge and it handles the merging at the best time, to save time and cycles to everyone. Homer bot, is a bot to explain clearly the workflow to help what should be mergeable, to avoid exactly the issue we just saw, or the issues we saw in the past on the ML, where people wanted to merge their code quicker than some reviewers were. Homer is configurable, but the idea is basically: - if you are dev/maintainer, and noone comments for x days, you can merge - if you are external/no commit access, you need at least one OK and y days, and one can merge- any discussion/thread opened blocks any merging, which allows someone to open a thread to say "I'm reviewing", "I have a doubt"Theres a cancel automerge button in forgejo
The automerging in Forgejo is not even close to what those bots do.It's simply an automatism for "Once all checks complete, and it still applies cleanly, merge it".
It does no CI checks again on the final state or anything, which a merge-bot implementing merge trains/a merge queue would do.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
