From ed5db9db1815af25aece61c5d988755519171bc4 Mon Sep 17 00:00:00 2001
From: Jim Myhrberg <contact@jimeh.me>
Date: Sat, 10 Jan 2026 07:12:07 +0000
Subject: [PATCH] fix(best-practices): replace force-with-lease article link

Replace the dead Atlassian blog link with a newer and more comprehensive
explanation of `git push --force-with-lease`, providing clearer context
for developers about this important git workflow practice.
---
 common-flow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common-flow.md b/common-flow.md
index 8e8967a..20c7654 100644
--- a/common-flow.md
+++ b/common-flow.md
@@ -251,7 +251,7 @@ interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
     3. You SHOULD always use "--force-with-lease" when doing a force push. The
        regular "--force" option is dangerous and destructive. More
        information:
-       <https://developer.atlassian.com/blog/2015/04/force-with-lease/>
+       <https://www.codestudy.net/blog/git-push-force-with-lease-vs-force/>
     4. You SHOULD understand and be comfortable with
        rebasing: <https://git-scm.com/book/en/v2/Git-Branching-Rebasing>
     5. It is RECOMMENDED that you always do "git pull --rebase" instead of "git