Splunk developers should have access to native source control that includes versioning, effect analysis, and rollbacks to previously stable versions.
There are some tools that sort of let you do this - including capturing the Splunk configuration changes (all the conf files) into GIT. Here is an old, but still insightful, video from a Splunk Conference some years ago: https://www.youtube.com/watch?v=-NIME9XRqlo
What is the question here? If you are proposing a new idea, please submit it to the Ideas section https://ideas.splunk.com/