On 13.02.2025 00:07, Soft Works wrote:
-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Timo
Rothenpieler
Sent: Mittwoch, 12. Februar 2025 22:33
To: ffmpeg-devel@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'm afraid, but from my point of view, this doesn't match the objective.
The only alternative is to completely lock down the instance, and not
allow new users at all without manual approval of each and every one.
People can just ask to be allowed to fork, but by default, allowing it
is not feasible.
Videolan apparently even went away from the current approach on our
instance, cause there was still too much spam. So they're
manual-approval-only now.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
