The problem with tracking configuration for
git is that all you really gain by doing so is version control (most
git novices don't even know how to
branch properly, so unlikely at that point) and the ability to rollback (again, if you aren't
tagging properly, you don't gain anything but a log to blame people); but you lose templating (cant template because git doesn't provide that), and scaling out (you cant apply the configuration anywhere else; especially if you are using distributed databases like Elasticsearch), and automated systems management (again, git doesnt provide this).
With that being said, what you are probably looking for is configuration management; that ties in templating,
git, and basic scripting to manage configuration. This, of course is going down the direction of DevOps and Infrastructure as Code.
To add to this; Ansible has
ansible-pull which can pull the latest repo of your playbooks from
git; the same is also true for Chef. Basically, modern Linux administrators shouldn't be using something like
etckeeper. Chef also has client-server mode where you can manage all systems with the
chef-client based on
roles, and cookbook versions; things you cannot do with
git solely and at scale.