If you haven't published the repository, then create commits out of your snapshots and rebase your branch on top of them.
If you have published the repository and your collaborators don't mind switching over to an entirely new rebased branch (which might require them to rebase their own changes), then you can do the same.
If you have published and you don't want to disturb anyone but still would like to add those commits for documentation purposes, you can create a new root branch separately. At this point you have a choice: leave it at that, or "attach" the branch to your main branch. By "attach", I mean "create a commit with both branches heads as parents, with the state of the main branch". You might call it a "merge commit", but obviously the branches aren't really "merged" since the main branch already reflects the appropriate state. For this, I'd point you to commit-tree
and write-tree
. This makes the commits easier to discover, though might be confusing to some. You'll probably want to backdate them, too.
Depending on what you choose, I encourage you to ask a new question or refine your current question.