Cloud Editor - bi-directional Git

I’ve recently setup my own provisioned cloud editor (will be sharing a blog post shortly). One of the issues that I’ve run into with the workflow is that gatsby-tinacms-git is only setup to push commits, never pull. Is that true? This means that if I (as a developer) ever make new commits on the branch that the cloud editor is pushing to, the subsequent cloud editor pushes will fail because the branch is not up-to-date with the remote. Is there any suggested way to deal with this? I was thinking that the cloud editor could send a subsequent pull API call if the push fails due to being out-of-date or maybe some sort of polling. Just a thought.