From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 058074009F for ; Tue, 12 Aug 2025 16:02:36 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 2540668CD29; Tue, 12 Aug 2025 19:02:33 +0300 (EEST) Received: from haasn.dev (haasn.dev [78.46.187.166]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 22B9668BBF4 for ; Tue, 12 Aug 2025 19:02:26 +0300 (EEST) Received: from haasn.dev (unknown [10.30.1.1]) by haasn.dev (Postfix) with UTF8SMTP id EB5C441C1E; Tue, 12 Aug 2025 18:02:25 +0200 (CEST) Date: Tue, 12 Aug 2025 18:02:25 +0200 Message-ID: <20250812180225.GB95324@haasn.xyz> From: Niklas Haas To: FFmpeg development discussions and patches In-Reply-To: References: <20250812090205.A5F4D68B0ED@ffbox0-bg.ffmpeg.org> <20250812113408.GB24045@haasn.xyz> <1bfcff88-d626-475b-a506-9d60feb5177e@gyani.pro> <20250812115108.GB29347@haasn.xyz> MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [FFmpeg-devel] Pushing without approval avfilter/vf_vignette: use AVFilterContext for logging X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: Tristan Matthews Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Tue, 12 Aug 2025 17:59:44 +0200 Kacper Michajlow wrote: > On Tue, 12 Aug 2025 at 14:35, Tristan Matthews via ffmpeg-devel > wrote: > > For reference, that's https://code.videolan.org/Garf/homer-bot > > Obviously that's gitlab specific but may help inform some choices here. > > Because of course there is homer-bot... I think everyone seen > marge-bot too https://github.com/smarkets/marge-bot (also GitLab > specific) > > Forgejo is API compatible with GitHub, so we could reuse solutions > that work there. Also in general Forgejo itself is more basic in > itself, doesn't support marge queues/trains, so any solution would > have to be a custom bot. For what it's worth, I was briefly discussing the idea of a merge bot with Timo over IRC, and the conclusion we arrived at is that we could also recreate the functionality of a merge queue that way. Basically, the merge bot would first rebase a PR, and only merge it once the CI passes - repeating as necessary until all "mergable" PRs are merged. > > - Kacper > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".