The article delves into the advantages of using an "environment-per-folder" approach over the "environment-per-branch" model in GitOps practices, specifically for managing Kubernetes manifests. The author critiques the branch-based method for its complexity and potential for error, advocating instead for organizing environments as folders within a single branch. This structure allows for straightforward promotion and modification of configurations across environments through simple file operations, eliminating issues associated with merging branches and configuration drift. The discussion includes practical examples of how to implement this approach using tools like Kustomize and Helm, highlighting the benefits of enhanced clarity and reduced risk in deployment processes. The author also addresses security concerns regarding the single-branch strategy, suggesting solutions such as using two separate repositories for production and non-production environments if necessary. Overall, the article aims to provide a comprehensive understanding of the folder method's benefits in streamlining GitOps workflows.