Reordering commits

You can use GitHub Desktop to reorder commits in your branch's history.

About reordering a commit

Reordering allows you to alter your commit history to provide a more meaningful progression of commits. GitHub Desktop allows you to drag-and-drop commits in your branch's history to reorder them.

Reordering a commit

  1. En GitHub Desktop, da clic en Rama Actual. Menú desplegable de la rama actual
  2. In the list of branches, click the branch with the commits that you want to reorder.
  3. Haz clic en History (Historial). La pestaña de historial seleccionada en la barra lateral
  4. Drag the commit that you want to reorder and drop it between two adjoining commits. reorder drag and drop While the application reorders the commits, a Reorder in process dialog indicates the progress of the change.

Error messages when reordering commits

When you reorder commits, you may see one of the following notifications or error messages.

  • A notification states that the requested change to the branch will require a force push to update the remote branch. This is shown when the commits that you reordered were previously pushed to the remote branch. Force pushing alters the commit history of the branch and will affect other collaborators who are working in that branch. Select Begin reorder to start the reorder, and then click Force push origin to push your changes.

    reorder force push dialog

  • An error states that the reorder failed because there is a merge commit among the reordered commits.

    reorder merge commit dialog

  • A notification is shown indicating that there are uncommitted changes present on your current branch. Select Stash Changes and Continue to store the changes and proceed, or select Close to dismiss the message and commit the changes. When there are no longer any uncommitted changes, you can reorder your commits.

    reorder stash dialog

  • A message states that there are merge conflicts that you must resolve before the application can continue reordering commits on your branch.

    1. Click View conflicts to see the conflicts.
    2. Resuelve cualquier conflicto de fusión que se produzca de la manera que prefieras, usando un editor de texto, la línea de comando o cualquier otra herramienta. Para obtener más información, consulta "Abordar conflictos de fusión."

    reorder resolve conflicts message

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.