Cool! Are you gonna try push your upstream changes back to fabric8 too so we don’t have 2 forks? :)
FWIW lots of changes have been made lately in the fabric8 forge REST service as we need to be able to support running of forge commands via a web console on lots of different git repos with different user secrets; so the REST API changed a reasonable amount lately to support user defined secrets (HTTP user/pwd or SSH keys) so that forge can operate on different git repos etc.
e.g. right now you can use the fabric8 console with JBoss Forge to edit and run commands on your github, bitbucket, Stash and on premise Gogs / GitLab repos; all from the same console.
If not using the secrets / git directly; I can see something like this being useful embedded into a web IDE where each user has their own local clone of source code on a persistent volume in a remote docker container which they then manage the git commit separately; but thats a bit harder & it looks like a real multi-user version of Che is a good few months away.
This is a separate work but based on the Fabric8 REST codebase.
The main idea is to bring the existing Fabric8 integration to the Forge organization, so different projects can adapt it as needed.