Eval/Test branches for scripts, automations and more

Hello,

in short: Some kind of version/branch-managemend would be nice.
Example:
When I escalate, creating new scripts/automations/helpers, I give the new
objects a name like a_lightsON1h_(EVAL)

But sometimes I’m kind of messy and do things quick and dirty.
So, why isn’t there an option to use an “EVAL” branch for scripts, helpers, automations and so on, so one could test and experiment and afterwards move objects from the non-production branch to the production branch?

Also some kind of tagging would be nice. E.g. the automation “a_lightsON1h” was created in my EVAL branch and got automatically or manual created a tag (like a coloured cirecle or/and word). So the object is easily traceable?

I searched for related topics, but did not found one, so If this is a double post, sorry.

Best regards,
Daniel

Duplicate from earlier today…
Test Suite for Blueprints.

That’s not exactly what I mean.
What I mean is some kind of GUI enhancement. Some kind of simple branch-
management.
The other post has context, but has not the same intention.

Another example:

You know that you can manage your configuration using git?

1 Like

Thanks for the info. I did not know about it.

But as I’m working with applications, which have this kind of feature out of the box, I stumbled across it in HA last time, when editing some automations.

To be fair, I don’t change things twice a week, but I know, this kind of posibility is fantastic - especialy, if you are not permanently dealing with HA as a hobby.