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.
This commit is contained in:
2026-01-10 07:12:07 +00:00
parent 5c18e04f90
commit ed5db9db18

View File

@@ -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 3. You SHOULD always use "--force-with-lease" when doing a force push. The
regular "--force" option is dangerous and destructive. More regular "--force" option is dangerous and destructive. More
information: 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 4. You SHOULD understand and be comfortable with
rebasing: <https://git-scm.com/book/en/v2/Git-Branching-Rebasing> 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 5. It is RECOMMENDED that you always do "git pull --rebase" instead of "git