1
deck
Essential Git Terminology (1)
| English Expression | Interpretation |
|---|---|
squash the last 3 commits | Combine the last 3 commits |
push commits to a repository | Deliver commits to a repository |
merge a feature branch into the base branch | Merge a feature branch into the base branch |
revert a pull request | Revert a pull request to its previous state |
request a review | Request a review |
comment on a pull request | Leave a comment on a pull request |
resolve a merge conflict | Resolve a merge conflict |
rebase onto another branch | Rebase onto another branch |
clone a repository | Clone a repository |
===
Essential Git Terminology (2)
| English Expression | Interpretation |
|---|---|
close a pull request without merging it into the branch | Close a pull request without merging it into the branch |
fork a repository | Copy a repository to create a new one in your account |
checkout a branch | Switch to a different branch |
stage changes for commit | Temporarily save changes for a commit |
pull the latest changes | Fetch the latest changes or code from a remote repository |
cherry-pick a commit | Selectively apply a specific commit |
amend a commit message | Modify a commit message |
discard uncommitted changes | Discard uncommitted changes |
===
Reference: What is Rebase?
Rebasing is a method of integrating changes from one Git branch into another. Unlike merging, it allows you to change the separated base to the latest base, keeping the history clean. It is useful for organizing the commit history, but it can cause conflicts during collaboration, so it should be used with caution.
Want to learn more?
Join CodeFriends Plus membership or enroll in a course to start your journey.