Results for “Commit history & revision selection”
Small, practical examples. Search by task or narrow things down below.
Rename a configured remote
Git: Renaming a remote updates its associated configuration and remote-tracking references.
Git✓ Tested
Rename the current branch
Git: branch -m changes the local branch name without creating a new commit.
Git✓ Tested
Replace the URL of a configured remote
Git: set-url changes configuration without fetching or pushing any objects.
Git✓ Tested
Replay an unpublished branch on a newer base
Git: Rebase updates the base of local feature commits when their changes do not conflict.
Git✓ Tested
Resolve a merge by writing the intended final file
Git: After a conflict, edit the result, stage it, and finish the merge commit.
Git✓ Tested
Restore the index state recorded in a stash
Git: Apply with index restores which changes were staged as well as their file contents.
Git✓ Tested
Return to the original branch
Git: Return to the original branch inside the disposable repository created by the input setup.
Git✓ Tested
See changed files
Show a concise working-tree status.
status✓ Tested
Set an author identity only for this repository
Git: Local configuration avoids changing the identity used by unrelated repositories.
Git✓ Tested
Stage a new file
Git: Stage a new file inside the disposable repository created by the input setup.
Git✓ Tested
Stage a tracked file rename
Git: Stage a tracked file rename inside the disposable repository created by the input setup.
Git✓ Tested
Stage one file
Add one changed file to the next commit.
add✓ Tested