Can I use Fetch in Version Control to write new workbenches to my Production Environment?

Hi 

Version Control in FME flow does work like this I am afraid. It is not integrated to that depth. When you fetch you are pulling down the history of workspaces and updating an internal FME database tables that holds GIT history details. There is no interactions with internal database tables that hold information such as parameters and parameter values, etc. 

For moving between environments, both Projects and Deployment parameters are very useful starts in moving between environments, and then there is more under the constant progression to CI/CD https://support.safe.com/hc/en-us/articles/25407510327437-Getting-Started-With-CI-CD-DevOps

I’m having difficulty understanding the purpose of Version Control in Flow then. Is this workflow, correct?  

1. Create a new workbench in FME Form and Publish to FME Flow.
2. Commit changes.
3. Fetch from Remote
4. Push to Remote.

At this point, my FME Flow and Git repository are both updated.

5. User downloads the workbench from FME Flow, makes some edits, re-publishes workbench.
6. Repeat steps 2-4.

FME Flow has the most recent version of the workbench, and Git repository have both historical versions.  

Unfortunately, the changes make in step 5 were a mistake and need to be rolled back. 

7. From the Workspaces page, the previous version can be viewed by clicking “History”
8.  downloading the correct version to the user’s desktop,
9. opening the workbench in FME Form,
10. and Republishing the Workbench to FME Flow,
11. Committing edits,
12. Fetching,
13. and Pushing to Remote.  

That is all correct above.

The key separation is between the Git and the FME Flow workings, is that the Fetch from Github does not update tables that are key to updating the “run workspace” UI. Instead, as you mentioned, you need to download the file and then republish it.

My pet peeve is that you can not also force users to commit, so the version you are running in FME Flow, may not be the same as the last commit shown in Git.