diff options
| author | Sytse Sijbrandij <sytses@gmail.com> | 2014-09-17 09:44:11 +0200 |
|---|---|---|
| committer | Sytse Sijbrandij <sytses@gmail.com> | 2014-09-17 09:44:11 +0200 |
| commit | 7ecc730a7ebf62de93bf36fa8bac0943609a7ca7 (patch) | |
| tree | 791593fd9f781cfdf590e2d812f5f392efaabb77 | |
| parent | 74fecb495cd8965d396d8943018f8042ea5d7f2e (diff) | |
| download | gitlab-ce-7ecc730a7ebf62de93bf36fa8bac0943609a7ca7.tar.gz | |
Add sentence about tools not being able to compensate for changing commit id's.
| -rw-r--r-- | doc/workflow/gitlab_flow.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md index 862bf027ab7..519111529a6 100644 --- a/doc/workflow/gitlab_flow.md +++ b/doc/workflow/gitlab_flow.md @@ -214,6 +214,7 @@ In conclusion, we can say that you should try to prevent merge commits, but not Your codebase should be clean but your history should represent what actually happened. Developing software happen in small messy steps and it is OK to have your history reflect this. You can use tools to view the network graphs of commits and understand the messy history that created your code. +If you rebase code the history is incorrect, and there is no way for tools to remedy this because they can't deal with changing commit identifiers. # Voting on merge requests |