[FFmpeg-devel] Regarding Git Tooling

[Jan Ekström]

On Wed, Jan 22, 2025 at 2:39 PM Nicolas George <george at nsup.org> wrote:
>
> Marth64 (12025-01-20):
> > This is fine and your preferences are understandable. Everyone has
> > their tools of choice.
> >
> > That said, I did try Forgejo on a local instance today without
> > JavaScript and it was not a usable experience for a contributor.
> > I could do some limited functions but not raise a PR, for example.
> > Besides this issue, the experience was pleasant and fast.
> >
> > Suppose there is an option with simple, reasonably, documented APIs
> > that can be used to bridge the gaps for our CLI-first developers.
> > Would you be open to experimenting?
> > Or as an output from this thread, can we declare what CLI-based user
> > workflows are needed
> > for folks to keep their velocity and start there? I imagine a creative
> > a solution can be found.
> >
> > Forgejo seems to have this: https://forgejo.org/docs/latest/user/api-usage/
> > I know from past experience managing a GitLab instance, it has APIs too.
>
> As long as the ability to use the solution with command-line tools is
> part of the scope statement of the project, I am absolutely fine testing
> any kind of solution.
>
> Frankly, it is already refreshing that the preference of people who want
> to work in command-line is taken into consideration at all and not just
> ignored or treated with scorn, as was so often the case in similar
> discussions.
>

For the record, usage via CLI/e-mail had been brought up by Anton (if
I recall correctly), and the CLI tooling for both Gitlab and
Gitea/Forgejo were looked into.

For Gitlab there is https://gitlab.com/gitlab-org/cli and for Forgejo
the current attempt at a solution seems to be
https://codeberg.org/Cyborus/forgejo-cli (the built-in forgejo-cli
seems to be for maintenance/administrative purposes). Both systems
base on HTTP APIs, so tooling around them can be written.

The initial result from testing was that the Gitlab option had many
more use cases implemented compared to the Forgejo one. Of course, if
such tooling is seen as important enough for FFmpeg's forge usage,
then it may make sense to put resources into developing this tooling
to improve the workflow for those who do not wish to utilize a web
browser.

Best regards,
Jan