A strict, correct and binding Git workflow document is urgently needed.
Not "an introduction to Git for dummies", not a list of tips and not a "best practices" document, but a complete document that would be strict and binding.
There's a page called Git/Workflow at mediawiki.org. I would expect it to be such a document, but currently it is:
- way too long
- not binding
- not controlled
- not actually used by a lot of frequent committers.
I tried to improve it as much as I could, but my git knowledge is very basic. Many other developers are saying the same.
Git can be a wonderful and ultra-flexible tool. People who know it well can juggle with it as much as needed. But when there are no stable procedures for updating the local repo and for committing a simple patch, a lot of people will waste hours on figuring out things that should take minutes. And new prospective developers WILL give up before submitting the first patch. I already saw it happen.
Version: unspecified
Severity: major
URL: https://www.mediawiki.org/wiki/Gerrit
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=35467
https://bugzilla.wikimedia.org/show_bug.cgi?id=35403