The article focuses on the pitfalls of using Git branches to manage different environments in GitOps practices, particularly when dealing with Kubernetes manifests rather than application source code. It argues that this approach, popularized by the Git-Flow model, is an anti-pattern due to the complexities and potential issues it introduces, such as merge conflicts, unwanted changes, and promotion order discrepancies. These challenges are exacerbated in large organizations with multiple environments, leading to configuration drift and management difficulties. Instead, the article emphasizes that tools like Helm and Kustomize advocate for using plain files and folders to model different environments, suggesting that this method is more aligned with GitOps principles and avoids the unnecessary complexity of branch-based environments.