Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create GitCherry.md #27

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create GitCherry.md #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions suggestions/GitCherry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
The git cherry command compares commits between two branches and displays the identifiers (hashes) of commits that exist in the development branch but have not yet been incorporated into the main branch.
This helps you quickly recognize the changes you've made that are yet to be merged into the main branch.

For instance, let's say you have a project with a main branch called "master" and a development branch called "feature."
You've made a few commits in the "feature" branch to work on a new feature. When you run git cherry master feature, Git will list the commits that are in the "feature" branch but haven't been merged into the "master" branch.
This provides a clear view of the changes that are pending integration into the main development line.

In summary, git cherry serves as a helpful tool to determine which commits have been applied to a specific branch and which ones are awaiting integration into another branch.
This is commonly used to keep track of the merging and feature development process in software projects.