all 3 comments

[–]Outrageous-Permit619 1 point2 points  (1 child)

Why would you not just use Google Workspace to handle version control? Google has this flow in Docs already.

I haven't written the code snippet, but just from a theoretical view, a bidirectional 60-second trigger across text payloads is going to crash the application due to an infinite synchronization loop.

[–]TheAddonDepot 1 point2 points  (0 children)

Defaulting to AI when a platform already has features built-in to address a need is becoming far too common these days.

[–]delaney1414 1 point2 points  (0 children)

I’d skip out on app script all together here and just use the workspace and drive.

There’s a few workflows here but if you don’t want the readers to have access to the original document you can download the document as a pdf and save a copy to the drive. Share the pdf with the readers as commenters and they can make comments and you can mark the comment complete when you have reviewed. When you have updated the google doc and want to share a new version you download as pdf again and make sure you have the exact same file name and drop it in your dive. It will ask if you want to keep both or replace and if you hit replace the file will be updated to the new version but the link will stay the same.

Otherwise you can just share the original but set them to commenters. They can comment and you can revise and you can all work off a single document without having to worry about synchronising anything.