Similar to how gitlab works. Being able maintain a single copy of a recipe and branching the master recipe to make changes then merge those changes back.
There tends to be much confusion when you copy because the new copy becomes the 'master' and receives updates. Copies can get lost and you don't necessarily want to modify a production recipe.
So the flow would be to branch that recipe, make changes and test, then merge to production quality recipe.
Thanks for reaching out! I just wanted to clarify this, so that our product team understands your needs. Is there a reason why testing and changes cannot be made to the original recipe so that you can click the update option in the copied recipe to merge the changes there? To avoid confusion, you can always rename recipes.
You could maintain 3 recipes (or more if you like):
Send us a ticket, we will try our best to assist you with your problem