A content file in Git is not automatically the source of truth
A repository copy can look authoritative after edits have moved to the CMS; label snapshots and decide where future changes belong.
An article was edited in the CMS while its earlier working copy stayed in the repository. The local file still looked tidy and reviewable. It just no longer matched the article people were maintaining. The problem was deciding which copy deserved to be trusted.
Before committing publishing copy, compare it with the current editor source and decide where future edits belong. If the CMS owns the content, a repository file needs either a deliberate synchronization process or an honest label such as “dated export” or “temporary draft.” Being next to the code does not make it current.
A dated export can still be a useful backup. It becomes misleading when someone treats that snapshot as the source for the next update. Version the reusable templates and publishing rules; keep article copies only with a clear purpose and a way to tell how old they are.