Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] forgejo merge vs approve
Date: Sun, 3 Aug 2025 17:04:10 +0200
Message-ID: <b732c2cf-9e8a-4086-af89-c72febef8caa@rothenpieler.org> (raw)
In-Reply-To: <20250803132600.GA29660@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 1125 bytes --]

On 8/3/2025 3:26 PM, Michael Niedermayer wrote:
> On Sun, Aug 03, 2025 at 01:45:17PM +0200, Timo Rothenpieler wrote:
>> On 8/3/2025 9:41 AM, Michael Niedermayer wrote:
>>> 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 ?
>>
>> That is how it should already work normally.
>> If there is no approval, the merge button turns into a "Auto-Merge when
>> checks succeed", and "at least one approval" is said check.
>>
>> Not sure if being an admin lets you bypass that, but at least I also see the
>> "Rebase then fw (When checks succeed)" button.
> 
> ok lets see if that works
> I saw one button and i clicked it on
> "https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20093"
> 
> lets see if it waits for an approval :)
> 
> btw how exactly does that work when a pull request crosses the area
> of knowledge of 5 people ?
You probably shouldn't mark such PRs for auto-merge on approval.
I'd only use it on more or less obvious/trivial things.

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4742 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

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

  parent reply	other threads:[~2025-08-03 15:04 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
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 [this message]
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=b732c2cf-9e8a-4086-af89-c72febef8caa@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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