diff options
| author | Freezed <git@freezed.me> | 2019-09-12 00:22:15 +0300 |
|---|---|---|
| committer | Freezed <git@freezed.me> | 2019-09-12 00:22:15 +0300 |
| commit | 2f236c206e04342f9b8445cef60e136a5cffecdc (patch) | |
| tree | 748d77d27419c3abc99f41d627c0be09ca7d4949 /doc/workflow | |
| parent | 76c0af2917550626c7ae9373933f274d6b845e0e (diff) | |
Update a dead external link
Diffstat (limited to 'doc/workflow')
| -rw-r--r-- | doc/workflow/gitlab_flow.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md index 2f365e42cc9..136e05281a6 100644 --- a/doc/workflow/gitlab_flow.md +++ b/doc/workflow/gitlab_flow.md @@ -1,4 +1,3 @@ - # Introduction to GitLab Flow  @@ -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. |