Great article! I too prefer using the term "DevSecOps". Despite causing confusion for some, having a variety of terms invites people to understand the nuances of the concept. The evolution of the term demonstrate DevOps itself! - Initially, there were very significant bottlenecks and lead time challenges due to interactions of Dev and Ops teams. As those have been resolved/improved, new bottlenecks with Security became visible. I can imagine that as other bottlenecks become significant for organizations/enterprises, the term DevSecOps will evolve again.
Maybe I'm missing something, but how does "git" come into this example? Is the script being saved as "git" - or are you registering a new sub-command?