opendev/gerrit
Code Issues Proposed changes

Merge branch 'stable-2.16' into stable-3.0

Browse Source 
* stable-2.16:
  Add 'Move a Change' section to user guide
  Move Api version for plugin manifests to non-stamped binary

Change-Id: I00e1184334a2f4cb540446e24634f2078c13499f
This commit is contained in:
David Pursehouse
2020-06-12 08:52:02 +09:00
parent 5b4548078c cea1b4dd5d
commit b1c0aa7cb6
2 changed files with 22 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
Documentation/intro-user.txt
View File

@@ -443,6 +443,23 @@ that there is still an interest in this change.
[NOTE]
Never rebase commits that are already part of a central branch.
[[move]]
== Move a Change
Changes can be link:rest-api-changes.html#move-change[moved] to a desired
destination branch in the same project. This is useful in cases where
development activity switches from one branch to another and there is a
need to move open changes on the inactive branch to the new active one.
Another useful case is to move changes from a newer branch back to an older
bugfix branch where an issue first appeared.
Users can move a change only if they have link:access-control.html#category_abandon[
abandon permission] on the change and link:access-control.html#category_push[
push permission] on the destination branch.
The move operation will not update the change's parent and users will have
to link:#rebase[rebase] the change. Also, merge commits cannot be moved.
[[abandon]]
[[restore]]
== Abandon/Restore a Change