The text discusses the debate surrounding the auto-sync feature in GitOps deployment tools like Argo CD and Flux, emphasizing the recommendation to always enable auto-sync unless there are exceptional circumstances. It argues that safety and control over deployments are primarily governed by Git permissions and processes such as pull requests (PRs), rather than the auto-sync feature itself. The author explains that enabling auto-sync allows the desired state in Git to be automatically synchronized with the actual state, reducing the need for manual executions like "argocd app sync." The text underscores the importance of defining everything as code and maintaining traceability through PRs, which offer security and prevent unauthorized access to production environments by limiting incoming traffic. The conclusion advocates for enabling auto-sync while controlling changes via Git permissions to ensure effective and secure deployments.