Could GIT manage revision headers embedded in code ?

Hello,

We need a great deal of traceability for our source, made of many scripts in interpreted languages, spread in many "independent" modules, as far as can be ;-). In particular, somebody troubleshooting a script in production should be able to know exactly the revision or commit ID (or tag label) of a given file, and its location in the GIT source directory tree.

Our old CVS... let's say it was its only advantage... was doing this with keywords embedded in code comments: $Header$, $Id$, $Rev$, $File$ etc... When a file was committed, its $Header$ keyword was expanded into a rich piece of "version" information like '' $Header: /cvsstore/SourcesOracle/Install/COMMUN/CST.sql,v 1.69.2.10 2017/04/14 09:38:48 edelanoe $".

Could this kind of "keyword expansion" feature be added into GIT ? Focusing on the goal: enable the identification of a file and its revision(*) inside the committed code itself. (*) the "revision" information or a commit ID. The tag(s) attached at commit time would be less reliable, as a tag can be moved between revisions.

Thank you in advance for any answer, Best regards, E.Delanoë

Grenobloise d'Electronique et d'Automatismes Inovallée - 12, Chemin de Malacher 38243 MEYLAN CEDEX FRANCE