Earlier quoted context omitted.
FFmpeg seems to have dealt with that problem when they still were on github. This is the paragraph at the end of the readme: > Contributing > Patches should be submitted to the ffmpeg-devel mailing list using git format-patch or git send-email. Github pull requests should be avoided because they are not part of our review process and will be ignored. An agentic LLM bot is likely to have no problems at creating a patc…
Why is it a major pain? Isn't it part of git workflow? Or is this because most developers got complacent in only using GitHub and similar?
one local repo per developer (or more repo if they wished so),
one central shared repo,
push a feature branch to the central repo,
somebody pulls the branch, reviews the changes and poss the merge them in the preproduction branch, or go back to the developer,
some test build deploy procedure,
acceptance tests, pass or go back to development,
merge in the production branch,
test build deploy.