Hello,
I’ve recently turned on Version Control a few days ago and just got around to setting up a Remote Repository (GitHub), I’ve just ‘pushed to remote’ for the first time, and I’ve noticed there are only 3 items on my GitHub repo, while I have 100+ workbenches uploaded.
I assume this has just uploaded items which have changed since I turned on Verion Control a few days ago. I was hoping enabling remote repo would push all of my workbenches to github.
What is the best way to proceed? I want to get all of the items uploaded to my github repo, not just changes, so I have a backup of all of the items on Flow.
Thanks.
Solved
Flow Version Control - How to get all of my workbenches on github?
+6- Supporter
Best answer by hkingsbury
You can leverage the REST API to automate this,
- make a call to get all the repositories - /repositories
- make a call to get all the items in each repository - /repositories/{repository}/items
- Next we need to make a POST call to /versioncontrol/commits/{repository}/{item}. This API isn’t documented. You can inspect the network calls when clicking the commit button in the UI to see the full call It just requires an empty json upload body
- The local repository will now be up to date, and from here you can go and manually push to the remote repository.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Did you add all your workspaces to the local repo before pushing to github?
From the command line, go to the folder with your workspaces and type
git ls-files
It will return a list of all files known to your git repository. If your workspaces aren’t listed, they aren’t managed by git, and you’ll have to add them to your repository first.
+30- Influencer
Hey Ecx,
It’s a common misconception to think that version control and the remote repository in FME Flow can be used like a regular Git workflow.
The Remote Repository in FME Flow is mainly intended as a backup mechanism. It stores the workspaces you’ve committed along with their version history, so you can preserve them during upgrades or migrations of FME Flow.
You won’t be able to interact with that remote repo directly. Only FME Flow itself should read from and write to it.
If your goal is to manage your workspaces with Git, I’d recommend setting up a separate Git workflow on your desktop environment, outside of FME Flow.
Draw it, map it, shape it, fix it, share it, change it, send, translate it 🎵
+65- Celebrity
- Best Answer
You can leverage the REST API to automate this,
- make a call to get all the repositories - /repositories
- make a call to get all the items in each repository - /repositories/{repository}/items
- Next we need to make a POST call to /versioncontrol/commits/{repository}/{item}. This API isn’t documented. You can inspect the network calls when clicking the commit button in the UI to see the full call It just requires an empty json upload body
- The local repository will now be up to date, and from here you can go and manually push to the remote repository.
+6- Supporter
You can leverage the REST API to automate this,
- make a call to get all the repositories - /repositories
- make a call to get all the items in each repository - /repositories/{repository}/items
- Next we need to make a POST call to /versioncontrol/commits/{repository}/{item}. This API isn’t documented. You can inspect the network calls when clicking the commit button in the UI to see the full call It just requires an empty json upload body
- The local repository will now be up to date, and from here you can go and manually push to the remote repository.
Thats exactly what I needed! Thank you!
The commit button under workspace you mentioned is also useful, to do it manually!
