Commit 6ead7b93 authored by Russell Dickenson's avatar Russell Dickenson

Merge branch 'aqualls-mermaid-diagrams3' into 'master'

Remove four-stages diagram from flow page

See merge request gitlab-org/gitlab!69516
parents d260d19c 93734dc1
...@@ -16,9 +16,16 @@ It combines [feature-driven development](https://en.wikipedia.org/wiki/Feature-d ...@@ -16,9 +16,16 @@ It combines [feature-driven development](https://en.wikipedia.org/wiki/Feature-d
Organizations coming to Git from other version control systems frequently find it hard to develop a productive workflow. Organizations coming to Git from other version control systems frequently find it hard to develop a productive workflow.
This article describes GitLab flow, which integrates the Git workflow with an issue tracking system. This article describes GitLab flow, which integrates the Git workflow with an issue tracking system.
It offers a transparent and effective way to work with Git. It offers a transparent and effective way to work with Git:
![Four stages (working copy, index, local repository, remote repository) and three steps between them](img/gitlab_flow_four_stages.png) ```mermaid
graph LR
subgraph Git workflow
A[Working copy] --> |git add| B[Index]
B --> |git commit| C[Local repository]
C --> |git push| D[Remote repository]
end
```
When converting to Git, you have to get used to the fact that it takes three steps to share a commit with colleagues. When converting to Git, you have to get used to the fact that it takes three steps to share a commit with colleagues.
Most version control systems have only one step: committing from the working copy to a shared server. Most version control systems have only one step: committing from the working copy to a shared server.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment