Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] forgejo merge vs approve
Date: Sun, 03 Aug 2025 18:06:18 +0700
Message-ID: <E1502A71-DE63-4977-8EE3-54925BEC7B38@remlab.net> (raw)
In-Reply-To: <20250803074153.GK1079928@pb2>



Le 3 août 2025 14:41:53 GMT+07:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>Hi
>
>can we have a tag that causes "automerge on approve" ?
>
>so that if i open a pr i can set that tag and if someone approves it, its
>merged and i dont have to come back and click that button ?

IMO, merging should be an explicit action, just to be on the safe side. It doesn't have to be by the submitter though.

The person approving might not realise that it will immediately merge, as that doesn't typically happen. Also they might just mean to approve whatever bit of the PR they feel competent about, and not necessarily the entire PR.


>
>thx
>
_______________________________________________
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".

  reply	other threads:[~2025-08-03 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-03  7:41 Michael Niedermayer
2025-08-03 11:06 ` Rémi Denis-Courmont [this message]
2025-08-03 11:45 ` Timo Rothenpieler
2025-08-03 13:26   ` Michael Niedermayer
2025-08-03 13:28     ` Michael Niedermayer
2025-08-03 13:30       ` James Almer
2025-08-03 13:53     ` James Almer
2025-08-03 15:04     ` Timo Rothenpieler
2025-08-03 14:01   ` James Almer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1502A71-DE63-4977-8EE3-54925BEC7B38@remlab.net \
    --to=remi@remlab.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git