Like DevOps, there’s not one single way to “do GitOps” nor a single checkoff list of tasks to implement, but let’s make this simple:
If I can determine the state and configuration of your infrastructure (and app code) by looking at Git commit logs, then you’re doing GitOps.
“Did she change the HTTP proxy to sticky sessions on the web front end yet?” - Look at Git logs
“What tests do we run on the API before the container image is uploaded to our registry” - Look at Git
“Did they upgrade the stagning cluster to Docker 19.03 yet?” - Look at Git logs
Sure, you may not have everything fully automated, even though automation is a big part of DevOps and GitOps. Remember that GitOps is more about having observability of change in a common place all the teams can see, and using those commits to kick off changes once you’ve automated things. Having a central place that all your tools connect to, and using that as the single-source-of-truth, is what will enable you to go faster and automate when you want to.