I don't know how feasible this is but my motivations for this are:
From an EGO reviewer's POV
(which I am not)
more familiar and (maybe?) better diff view, tooling etc.
pipeline for automated initial testing/review
e.g. there is an idea floating around of making a minimal eslint config mandatory for extensions
From an extension dev's POV
Extending (heh 🙃) the idea of a pipeline... if an extension dev could write some CI/CD themselves (which ofc should be reviewed as well), they wouldn't be limited to writing extensions in plain javascript. For instance, I am interested in using typescript. Currently, I would need to transpile it to JS before uploading it to EGO, then the review would happen with the transpiled files. That's not ideal... the resulting JS can be hard to read, especially when using non-native features like decorators. Reviewing the 'actual source code' would probably be better. A CI/CI pipeline could also make the 'release uploading' less manual for extension devs.