GitLab treats a Git repository mainly as an append only store right now. It's made very easy to append a new commit to their parent, and grow the repository. Developers are left to their local machine when advanced they want to go outside this scope. Simple actions developers should be able to perform through GitLab: 1. Reword a commit message 1. Dropping a commit from a branch (not the default one) 1. Reorder commits in a branch This is very similar to what `git rebase --interactive` provides on the command line interface, for example: ``` pick 82910d93004 Support adding and removing assignees w/ push opts pick 908220c4bff Add filter_assignees_with_key() to issuable_base_service # Rebase 7e42320948a..b567393f90b onto 7e42320948a (20 commands) # # Commands: # p, pick <commit> = use commit # r, reword <commit> = use commit, but edit the commit message # e, edit <commit> = use commit, but stop for amending # s, squash <commit> = use commit, but meld into previous commit # f, fixup <commit> = like "squash", but discard this commit's log message # x, exec <command> = run command (the rest of the line) using shell # b, break = stop here (continue rebase later with 'git rebase --continue') # d, drop <commit> = remove commit # l, label <label> = label current HEAD with a name # t, reset <label> = reset HEAD to a label # m, merge [-C <commit> | -c <commit>] <label> [# <oneline>] # . create a merge commit using the original merge commit's # . message (or the oneline, if no original merge commit was # . specified). Use -c <commit> to reword the commit message. # # These lines can be re-ordered; they are executed from top to bottom. ``` If the API is the same, this would be reasonably easy to implement on both the Rails side, as well as Gitaly, and be very flexible. Problems remain conflict resolution, which to fix properly will take multiple iterations.