Overwriting Adobe Launch code/version control

[Meghan_Powers]

A big pain point for our team and I’m sure many teams is the lack of version control in Adobe Launch/Tags.  It’s really easy for our developers to overwrite each other’s code without realizing it, to be mixed up in the same libraries, and for code to go to prod that was not supposed to go to production.  I would love some recommendations from you all on ways to mitigate this, what you’ve seen other clients do, what are typical best practices, what does Adobe offer to keep this from happening, or from happening less.
It's not the first time, but we just had an issue where someone saved the word 'test' in a pagename, and saved it many many versions ago.  Then someone came along 20 versions later and unknowingly published that change to production.

[bjoern__koth]

Been there as well. Typically, Launch will inform you if your library contains a version of a particular rule or data element that has been outdated in the meantime, and typically what devs is just update their version a little carelessly.

This is what causes the issues I think l.

There are no branches, merges and pull requests one may know from source code versioning.

I would love to have a library act as a branch that remains by itself and does not impact the other branches until I want to merge it onto Stage or Prod.

The same way I can discard a branch like that without impacting the other existing branches / libraries.

Surely one of my top wishes