Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests

[Soft Works <softworkz-at-hotmail.com@ffmpeg.org>]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Gyan
> Doshi
> Sent: Donnerstag, 13. Februar 2025 10:49
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
> 
> 
> 
> On 2025-02-13 02:19 pm, Leo Izen wrote:
> > On 2/12/25 5:05 PM, Timo Rothenpieler wrote:
> >>>
> >> I'm really not sure what you're asking.
> >> PRs are not restricted. Creating repos is.
> >> And there is no way to NOT restrict it, unless you want to pay
> >> several hundred Euros a month in hosting fees extra, and constantly
> >> be on the lookout for hosting illegal/harmful things.

Hi Leo,

> > My understanding as a Github and Gitlab user is the usual way to make
> > a PR is to first fork the repository, then commit changes to a branch
> > on your fork, and then send a PR which compares the fork to the master
> > branch of upstream.

Yes exactly!


Hi Gyan,

> For some time, Github has allowed in-place editing. What that means is
> once you finished editing the file in the upstream repo, GH will fork
> the repo for you, or if already forked, create a new branch, with your
> changes incorporated, and give you an option to send a PR.

That's right. It still does that (for clarification: this is about making edits in the GH WEB UI).
It's pretty convenient for small edits at times. Yet, it's not a different procedure, it just creates a fork and a branch in the fork for you plus a commit with your changes automatically in one go on a single Save button click.
The fork it creates (if you don't have one) is a normal fork like any other fork you create manually.

Best
sw

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