Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Alexander Strasser via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Alexander Strasser <eclipse7@gmx.net>
Subject: Re: [FFmpeg-devel] forgejo merge vs approve
Date: Mon, 4 Aug 2025 22:39:55 +0200
Message-ID: <aJEam9V8WVZ2XDkb@metallschleim.local> (raw)
In-Reply-To: <b732c2cf-9e8a-4086-af89-c72febef8caa@rothenpieler.org>

On 2025-08-03 17:04 +0200, Timo Rothenpieler wrote:
> 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.

Fully agree with Timo.

One should act responsibly and only use auto-merge on very small, mostly
trivial changes.

For bigger stuff I think it's best to let either the main author or the
main reviewer do the merge.

Where the author is only possible when they have write access and
with main reviewer I mean a reviewer that fully reviewed the changes and
not only partially.

This is usually the best option because they have a better mental model
of how things work and what gets changed and don't want to introduce
errors themselves when actively merging the changes. So things that might
have been not found yet still have a good chance to pop up last minute.


  Alexander
_______________________________________________
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-04 20:40 UTC|newest]

Thread overview: 10+ 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
2025-08-04 20:39       ` Alexander Strasser via ffmpeg-devel [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=aJEam9V8WVZ2XDkb@metallschleim.local \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=eclipse7@gmx.net \
    /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