Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PTP/environment setup/git"
(→Reverting Commits) |
(→Reverting Commits) |
||
| Line 57: | Line 57: | ||
=== Reverting Commits === | === Reverting Commits === | ||
| − | There are two ways to revert commits in git. You can either add a new commit that reverts a previous commit, or you can tell git to reset the branch to a prior commit. The former is much safer, since it functions like any other commit and does not change the revision history prior to the commit. Also, this will only revert the selected commit. The latter operation, however, will erase all trace of all commits after a selected commit. This can be useful for commits that were made in error. However, | + | There are two ways to revert commits in git. You can either add a new commit that reverts a previous commit, or you can tell git to reset the branch to a prior commit. The former is much safer, since it functions like any other commit and does not change the revision history prior to the commit. Also, this will only revert the selected commit. The latter operation, however, will erase all trace of all commits after a selected commit. This can be useful for commits that were made in error. However, you should never reset commits that are already pushed to remote. Only use this for recent commits made in your local workspace. Otherwise, you will not be able to push your changes to remote, since our remote server is configured to not allow modifications to history. |
To undo commits, select a commit in the history view and right-click. Selecting 'Revert Commit' does the safer option described above. Selecting 'Reset' -> 'Hard' does the unsafe method and will erase all commits after the selected commit. | To undo commits, select a commit in the history view and right-click. Selecting 'Revert Commit' does the safer option described above. Selecting 'Reset' -> 'Hard' does the unsafe method and will erase all commits after the selected commit. | ||
Revision as of 15:41, 8 November 2011
The transition is currently being planned in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=349695
Contents
Documentation
- http://www.youtube.com/user/cdtdoug (CDT screencasts - last 7 videos are about GIT)
- http://wiki.eclipse.org/EGit/User_Guide
- http://wiki.eclipse.org/Git
- http://wiki.eclipse.org/Platform-releng/Git_Workflows
- http://veerasundar.com/blog/2011/06/git-tutorial-getting-started/ - nice beginning tutorial esp. describing local vs. remote repository and a nice diagram of Git Data Transport Commands
Things I Used To Be Able To Do Using CVS
Here are some things that I used to be able to do using CVS, but are either difficult or I can't work out how to do them using Git/EGit
Managing Two Branches
Say I had two branches A and B. If I added a new file (plugin, whatever) to branch A, I'd just commit it then switch over to branch B (I might have two workspaces set up, one with branch A and one with branch B). The I'd use Team>Compare With>Another Branch or Version... and add/replace any changes. Then I'd commit to branch B.
Using EGit, I need to show the history view in branch B then cherry pick the change from branch A I want (assuming it shows in the view, which sometimes it doesn't seem to). The problem with this it that you need the file to exist in the target branch before you can show it in the history view. How do you do it when a new file is added?
Answer: Select the folder or package that should contain the new file and select the history view. In the history view, select "Show All Branches and Tags" (blue arrow icon at top right) and cherry pick as usual.
Creating Patches
If I had some uncommitted changes in my workspace, I could just say Team>Create Patch... to save a patch of the changes. In EGit, it seems you have to commit the changes first. How do I create a patch without committing changes?
Answer: It seems you cannot. I would suggest to commit the change in a temporary/feature branch. Team->Switch To->New Branch Team->Commit
Reverting Changes
If I had a changed file in the workspace, I could just revert it using Replace With... For EGit I don't always get the option? What gives?
Feedback: In what cases does it not work?
Other Questions I Have About EGit
Comparing
I try to compare my local copy of branch A using Compare With>Branch, Tag, or Reference... then selecting origin/branch B from Remote Tracking. However it doesn't show all the changes even though I know they are there. Why is that?
Answer: The most likely reason is that you didn't push (for local changes) or pull (for remote changes). If these changes were made locally and you have committed them but not pushed yet than the changes are only in the local branch B not the remote tracking branch B. In that case you should compare to the local branch B or push before you compare. If the changes were done remote (in a different repository) you need to pull (or fetch) to update the remote tracking branch to the new version. The history view helps visualizing to which version each branch points.
Cherry Picking
If I cherry pick some changes from one branch to another, do I need to commit it? Or is it just done? How do I revert it if need to?
How do I only apply some of the changes from a particular commit? Cherry picking only seems to apply them all.
Answer: Cherry picking a commit automatically commits it to the destination branch (adds a commit with the same commit message). So reverting this commit is the same as reverting any other commit (see below).
Applying only part of a commit is more difficult. In this case, you will need to either apply the changes without cherry picking or cherry pick and reverse the changes not needed. (Note that git works best if commits are small and frequent, with each commit representing a single "logical" change, which may span any number of files.)
After cherry picking, you can right-click on the project and select 'Compare With...' -> 'Previous Revision' to open a Git Tree Compare view and undo any unwanted changes. Then commit these changes with "Amend Previous Commit" selected, so that the cherry pick and these changes are all contained in a single commit.
Reverting Commits
There are two ways to revert commits in git. You can either add a new commit that reverts a previous commit, or you can tell git to reset the branch to a prior commit. The former is much safer, since it functions like any other commit and does not change the revision history prior to the commit. Also, this will only revert the selected commit. The latter operation, however, will erase all trace of all commits after a selected commit. This can be useful for commits that were made in error. However, you should never reset commits that are already pushed to remote. Only use this for recent commits made in your local workspace. Otherwise, you will not be able to push your changes to remote, since our remote server is configured to not allow modifications to history.
To undo commits, select a commit in the history view and right-click. Selecting 'Revert Commit' does the safer option described above. Selecting 'Reset' -> 'Hard' does the unsafe method and will erase all commits after the selected commit.
Merging
If I cherry pick some changes my local workspace seems to be in some kind of merged state (e.g. [org.eclipse.ptp|Merged master]). If I commit, EGit forces me to commit all changes in the workspace, not just the ones I select. I may have changes that I don't want to commit right now. What do I do?
Notes
- In CVS, HEAD means the 'branch' that is the latest most recent main work
- In GIT, HEAD is the endpoint of a branch. 'master' is the 'branch' that is the latest most recent main work
- So, there is a HEAD revision of each branch, which is the endpoint (last change).
- E.g. there is the HEAD of master and the HEAD of ptp_5_0
- In GIT, HEAD is the endpoint of a branch. 'master' is the 'branch' that is the latest most recent main work
- 'Origin' is the default name of the remote repository on eclipse.org