Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

Most of your answer looks ok, until this "especially if people properly rebase their work before merging or pushing" Cherry picking and rebasing is essentially the same thing. They both causes history losses and they both invalidate any testing you've done on the picked commits. Rebasing is really just cherry picking on steroids.

Lie Ryan
– Lie Ryan

2020-04-21 17:00:59 +00:00
Commented Apr 21, 2020 at 17:00
2

@LieRyan: Yup. With the exception in this case that rebasing is done on your own history, but the OP was cherry-picking commits between public branches. That invalidates the testing done by the entire team, not just your own testing.

Greg Burghardt
– Greg Burghardt

2020-04-21 17:55:36 +00:00
Commented Apr 21, 2020 at 17:55

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »