When collaborating on documents, sometimes it may be necessary to make a copy to make individual annotations. However, making a copy will not keep other annotations up-to-date/synced with the master/main copy. Thus, a feature allowing users to “fork” a document and keep it synced while adding their own edits in their forked document would be useful. This is important and especially essential for educational settings where a teacher or project leader may wish to distribute a template version for individuals to edit, but keep annotations or edits updates on all copies.
A further extension to this would be the ability to make pull requests back to the original document and merging from forks. This will be very useful for collaborative note-taking.
ljx1608 supported this idea ·
When collaborating on documents, sometimes it may be necessary to make a copy to make individual annotations. However, making a copy will not keep other annotations up-to-date/synced with the master/main copy. Thus, a feature allowing users to “fork” a document and keep it synced while adding their own edits in their forked document would be useful. This is important and especially essential for educational settings where a teacher or project leader may wish to distribute a template version for individuals to edit, but keep annotations or edits updates on all copies.
A further extension to this would be the ability to make pull requests back to the original document and merging from forks. This will be very useful for collaborative note-taking.
Related suggestion: https://feedback.goodnotes.com/forums/191274-customer-suggestions-for-goodnotes/suggestions/40310119-move-annotations-to-a-new-pdf
Inspiration for this suggestion comes from cloning/forking repositories in source code version control systems like Git.