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

[Tomas Härdin]

ons 2025-02-12 klockan 23:07 +0000 skrev Soft Works:
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> > Timo
> > Rothenpieler
> > Sent: Mittwoch, 12. Februar 2025 22:33
> > To: ffmpeg-devel at ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull
> > requests
> > 
> > On 12.02.2025 22:22, Stephen Hutchinson wrote:
> > > Are all accounts restricted to owning a maximum of 0 repositories
> > > by
> > > default, or is it set to 0 only for those that sign up through
> > > one of
> > > the external logins?
> > 
> > It's set to 0 by default, to avoid spammers uploading junk, or just
> > people (ab)using it for non-ffmpeg things.
> > 
> > You can open issues and comment on existing PRs.
> > And also create PRs using the AGit workflow:
> > https://forgejo.org/docs/latest/user/agit-support/
> 
> For those who are too lazy to look it up:
> 
> The "Agit workflow" requires you to use non-standard Git "push-
> options"
> (either -o or --push-options):
> 
> git push origin HEAD:refs/for/master -o topic="topic-branch" \
>   -o title="Title of the PR" \
>   -o description="# The PR Description
> This can be **any** markdown content.\n
> - [x] Ok"
> 
> This means essentially that our attempt to move away from the e-mail-
> based submission procedure to something easy and user-friendly, would
> end up in replacing the current rarely-known mechanism with another
> even more rare and obscure procedure which would (again) force
> everybody to use the Git command line because it's (again) not
> supported by any tooling except Git CLI.

I see this as a plus. More stuff should be done with git alone. This is
one case where fossil shines, because it combines code, tickets and
wiki into one single CLI tool.

/Tomas