Merge branch 'patch-72' into 'master'

Update a dead external link in documentation See merge request gitlab-org/gitlab-ce!32939

Merge branch 'patch-72' into 'master'
Update a dead external link in documentation See merge request gitlab-org/gitlab-ce!32939
a52935fb · Ray Paik · 1cef292c · 2f236c20 · a52935fb
--- a/doc/workflow/gitlab_flow.md
+++ b/doc/workflow/gitlab_flow.md
-
 # Introduction to GitLab Flow

 ![GitLab Flow](img/gitlab_flow.png)
@@ -60,7 +59,7 @@ For example, many projects do releases but don't need to do hotfixes.
 In reaction to Git flow, GitHub created a simpler alternative.
 [GitHub flow](https://guides.github.com/introduction/flow/index.html) has only feature branches and a `master` branch.
 This flow is clean and straightforward, and many organizations have adopted it with great success.
-Atlassian recommends [a similar strategy](https://www.atlassian.com/blog/archives/simple-git-workflow-simple), although they rebase feature branches.
+Atlassian recommends [a similar strategy](https://www.atlassian.com/blog/git/simple-git-workflow-is-simple), although they rebase feature branches.
 Merging everything into the `master` branch and frequently deploying means you minimize the amount of unreleased code, which is in line with lean and continuous delivery best practices.
 However, this flow still leaves a lot of questions unanswered regarding deployments, environments, releases, and integrations with issues.
 With GitLab flow, we offer additional guidance for these questions.