---
title: "Discussion on \"Your Deploy Button Should Be a Git Commit, Not a Click\" | Hashnode"
description: "Discussion on \"Your Deploy Button Should Be a Git Commit, Not a Click\". A deploy that's a `git revert` away from undone behaves completely differently than one that needs a person to remember the manual steps backward. GitOps and progressive delivery are the two practices that make that true, plus a real proptech recovery-time story: 5 hours down to 12 minutes."
url: "https://hashnode.com/posts/gitops-progressive-delivery-pattern/6ac631777bc6fbe376acf7f0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Your Deploy Button Should Be a Git Commit, Not a Click](https://sherdil-cloud.hashnode.dev/gitops-progressive-delivery-pattern?utm_source=hashnode&utm_medium=feed)

A deploy that's a \`git revert\` away from undone behaves completely differently than one that needs a person to remember the manual steps backward. GitOps and progressive delivery are the two practices that make that true, plus a real proptech recovery-time story: 5 hours down to 12 minutes.

Oct 7 · 6 min read · sherdil-cloud.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)
-   [#gitops](https://hashnode.com/tag/gitops)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#argocd](https://hashnode.com/tag/argocd)

## Written by

[Sherdil Cloud](https://hashnode.com/@sherdilcloud)

@sherdilcloud

  
[View profile](https://hashnode.com/@sherdilcloud)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
