Commits

How it works

1. Open the git view. The sidebar turns to its history: Uncommitted changes first, then the branch's commits under a heading for each day, newest first, each led by its author's initials.
2. Press a commit to see its hash, tree, author, date and parent, and under them every file it changed, each opening to its diff.
3. Load more, at the foot of the list, reads further back.
4. Push, at the head of the view, sends your commits to the remote and shows how many are waiting. A branch with no upstream yet offers Publish branch instead.

Good to know

• The arrow beside Push holds Force push with lease and Force push, which asks first, since it overwrites the remote's history.
• A warning on Push says when the branch and its remote have both moved on.
• Right-click a commit for Copy commit message, Copy commit hash and Soft reset HEAD to this commit, which keeps your files and uncommits everything after it.
• Origami does not pull: run git pull in a terminal.

Related

• ChangesThe git view's first page, where you read, stage and commit what has changed in a workspace's folder.
• BranchesSwitch, create, rename and delete a workspace's branches from one page of the command palette.
• Branch reviewEverything the current branch changes since it left its base, committed or not, as one diff.