I have been manually using GitHub Desktop to revision control my surveys for a while now, and it dawned on me that it may be simple to create a GIT integration for Connect that would streamline my workflow since Connect already has access to running scripts in the terminal. Here is the concept:
The home view would allow you to configure your 'user/ArcGIS\My Survey Designs' as a git repo and perform global pulls from remotes. Global pushes could potentially be done, but I think the workflow would be better served to push these from individual surveys so that users new to the process don't get into the habit of sloppy commit messages. The exception to this list would be deletions, which may require a special commit and push, but a radio option to include the GIT process could trigger this during a delete prompt if GIT were configured.
Inside an individual survey, there would be a pull/rebase option, a commit option, and, if commits are staged, a push option.
As an example, I use VS Code's built-in GIT integration for my Python development. While the learning curve can be steep for new users, it is relatively simple to train people and arguably much less complicated than most of the "Tricks of the Trade" topics. If used correctly, the primary benefit would be traceability and rollback, with a potential for concurrent development. There would also be the potential of a CICD process for form development when the Python S123 implementation is fully developed, which I haven't seen in any other Survey toolchain yet, as long as the end form pointer (currently in settings) could be configured as part of the runtime.
