Seeing all of the above, plus:
Click 'Pull' > "We were unable to complete the pull because you have uncomitted changes. Please commit first before attempting to pull again"
Click 'commit': "There are no changes to commit."
Click 'Pull' again> it pulls as expected.
4. The bigger problem now is, you get all the changes/commits made by other developers as your own local changes when you do a pull. Isn’t it weird?
I do hope that there will be a solution here soon. It is now very difficult to see which developer has made which change. Very weird behaviour.
2. Sometimes without any changes in studio pro, due to some unwanted changes in disk, it doesn’t allow to pull, resulting in false or unnecessary commits
What we do in this case is "Version Control” → "Revert All Changes”, and then do the pull. This prevent the unnecessary commit, and we haven't seen any side effects so far.
relates to this idea
https://forum.mendix.com/link/space/databases/ideas/4189
you can use TortoiseGIT