Question about tagging in a mirror before mirroring deletions
Inner struggles of a digital hoarder vs minimalist (or having your cake and eating it too).
The context: A feature branch contains dozens of commits during development of the feature. Sometimes it also has branches off it, exploring alternative implementations. Once the feature is complete, it gets committed into a main branch as a single commit - compressing all that history - then the feature branch is deleted.
The question: Is there a way to save that history in a mirrored repository - something that keeps the main repo clean, but allows looking back at everything in a separate archive if desired.
Tagging seems like the right solution, but I'm concerned about optimizing both visual clutter and storage/performance on the main repository, so tagging on the main repo doesn't seem like a good plan.
How would you automate tagging in the mirror before mirroring deletions?
(the primary repository is hosted on Bitbucket Server. The mirror could be on BitBucket, or GitLab, or just a random machine with a cron job)
Posted Oct 14, 2016, 2:22 PM UTC
If you want to push your branch, before compression, to another remote, it's not too hard.
Wherever you're centrally tracking your repo, create a new repo, add it as a remote, push the branch before compression to that remote, and then you have it stashed somewhere for reference.