Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EGit/New and Noteworthy/1.1"

(Commit Dialog Improvements)
(Commits)
(9 intermediate revisions by 5 users not shown)
Line 8: Line 8:
  
 
== Allow dragging of commits from History view ==
 
== Allow dragging of commits from History view ==
 +
 +
You're now able to Drag and drop commits either onto a Mylyn Task or into a folder on your harddisk. In both cases, EGit will automatically create a patch for you to attach it on the bug or to create a patchfile on your harddisk.
 +
 +
[[Image:Dnd patch.png]]
 +
 
== New preference to ignore whitespace changes in blame annotations ==
 
== New preference to ignore whitespace changes in blame annotations ==
 
== History View always displays HEAD and other additional refs ==
 
== History View always displays HEAD and other additional refs ==
Line 31: Line 36:
 
== New Features in Synchronize View ==
 
== New Features in Synchronize View ==
 
* Synchronize filtered on folder
 
* Synchronize filtered on folder
* drag and drop staging / unstaging in Git Changeset Model
+
* drag and drop staging / unstaging in Git Changeset Model ([http://www.youtube.com/watch?v=MU9eaf_rSWw demonstration on youtube])
 
* new "Fetch Changes" checkbox in synchronize wizard
 
* new "Fetch Changes" checkbox in synchronize wizard
 
* Performance improvements
 
* Performance improvements
 +
* "Synchronize Wizard" allow select additional refs like FETCH_HEAD
 +
* "Synchronize With..." menu item moved into "Advanced" section
  
 
== Team Project Set Support ==
 
== Team Project Set Support ==
 +
 +
It's now possible to export and import Git projects with team project set files (.psf). This enables easier workspace setup, especially with many repositories and/or with different branches. How it works:
 +
 +
* Select the projects you want to export
 +
* Right click on the selection and chose ''Export''
 +
* Select ''Team Project Set''
 +
* Fill in the details such as where the ''.psf'' file should be saved and finish the wizard
 +
 +
This creates a file with all the information that is necessary for Eclipse to reconstruct the project setup. It contains the URLs of the Git repositories, the branch to checkout, and the paths to the projects. Creating a new workspace is as easy as:
 +
 +
* Go to ''File'' -> ''Import''
 +
* Select ''Team Project Set''
 +
* Select the ''.psf'' file
 +
 +
Eclipse will clone the repositories into the workspace location, check out the right branches and import the projects, ready for creating new commits and pushing.
 +
 
== Logical Model Support ==
 
== Logical Model Support ==
* consider logical model when staging files
+
 
* consider logical model when replacing files
+
In case you're working with files that are supported by a Logical Model Provider (eg. EMF Compare for .ecore, or other commercial modeling tools), EGit now detects these cases during staging, replacing and commiting changes and will help you to choose the right set of files to work on.
* consider logical model in commit action
+
 
 +
[[Image:EGit logical Selection.png]]
 +
 
 +
For some background information on Logical Models, see this blog post: [http://tasktop.com/blog/eclipse/what-the-heck-are-logical-models What the heck are Logical Models]
 +
 
 +
== Navigating from tasks to commits ==
 +
 
 +
With the Mylyn/EGit bridge installed, you're now able to see commit ids in tasks (eg. Bugzilla) hyperlinked. Once clicked, the corresponding commit will open up in the Commit Editor.
 +
 
 +
[[Image:Mylyn commit links.png]]
  
 
= New Actions =
 
= New Actions =
Line 67: Line 99:
 
* The GitHub Java API now supports the entire [http://developer.github.com GitHub v3 API]
 
* The GitHub Java API now supports the entire [http://developer.github.com GitHub v3 API]
 
* The README is available [http://egit.eclipse.org/w/?p=egit-github.git;a=blob_plain;f=org.eclipse.egit.github.core/README.md;hb=refs/heads/stable-1.1 here]
 
* The README is available [http://egit.eclipse.org/w/?p=egit-github.git;a=blob_plain;f=org.eclipse.egit.github.core/README.md;hb=refs/heads/stable-1.1 here]
** Rendered version available [https://github.com/eclipse/egit-github/tree/stable-1.1/org.eclipse.egit.github.core here]
+
** Rendered version available [https://github.com/eclipse/egit-github/tree/stable-1.1/org.eclipse.egit.github.core#readme here]
 +
 
 +
 
 +
= Commits =
 +
 
 +
[http://egit.eclipse.org/w/?p=egit.git;a=shortlog;h=stable-1.1;hp=v1.0.0.201106090707-r;opt=--no-merges EGit 1.1 - commits in gitweb]

Revision as of 18:58, 7 December 2011

New Features

New Reflog View

  • Shows the Git reflog for a selected repository
  • Supports showing the reflog for a specific branch by selecting the hyperlink ref name in the top right of the view
  • Supports searching and filtering
  • Double-clicking a reflog entry opens the corresponding To commit

Egit11-reflow-view.png

Allow dragging of commits from History view

You're now able to Drag and drop commits either onto a Mylyn Task or into a folder on your harddisk. In both cases, EGit will automatically create a patch for you to attach it on the bug or to create a patchfile on your harddisk.

Dnd patch.png

New preference to ignore whitespace changes in blame annotations

History View always displays HEAD and other additional refs

More information displayed in merge, fetch and push results dialogs

  • Commits and modified files displayed in fetch, push, and pull and push result dialogs
  • Commit details such as author and date are now displayed for merge results
  • Icons displayed for different ref update types (new tag, new branch, etc.)
  • Push result messages now support hyperlinks

Egit11-pull-results.png

Egit11-push-results.png

Commit Dialog Improvements

  • Support for commit ID hyperlinks
  • Content assist for file names shown in Files section

Egit11-commit-content-assist.png

Staging View

  • New column layout preference that supports showing the Unstaged Changes and Staged Changes sections side by side
  • New preference for showing the file names first followed by the directory that the files are located in

Egit11-staging-view.png

New Features in Synchronize View

  • Synchronize filtered on folder
  • drag and drop staging / unstaging in Git Changeset Model (demonstration on youtube)
  • new "Fetch Changes" checkbox in synchronize wizard
  • Performance improvements
  • "Synchronize Wizard" allow select additional refs like FETCH_HEAD
  • "Synchronize With..." menu item moved into "Advanced" section

Team Project Set Support

It's now possible to export and import Git projects with team project set files (.psf). This enables easier workspace setup, especially with many repositories and/or with different branches. How it works:

  • Select the projects you want to export
  • Right click on the selection and chose Export
  • Select Team Project Set
  • Fill in the details such as where the .psf file should be saved and finish the wizard

This creates a file with all the information that is necessary for Eclipse to reconstruct the project setup. It contains the URLs of the Git repositories, the branch to checkout, and the paths to the projects. Creating a new workspace is as easy as:

  • Go to File -> Import
  • Select Team Project Set
  • Select the .psf file

Eclipse will clone the repositories into the workspace location, check out the right branches and import the projects, ready for creating new commits and pushing.

Logical Model Support

In case you're working with files that are supported by a Logical Model Provider (eg. EMF Compare for .ecore, or other commercial modeling tools), EGit now detects these cases during staging, replacing and commiting changes and will help you to choose the right set of files to work on.

EGit logical Selection.png

For some background information on Logical Models, see this blog post: What the heck are Logical Models

Navigating from tasks to commits

With the Mylyn/EGit bridge installed, you're now able to see commit ids in tasks (eg. Bugzilla) hyperlinked. Once clicked, the corresponding commit will open up in the Commit Editor.

Mylyn commit links.png

New Actions

  • Staging View
    • unstaged pane: "Add to Git Index", "Replace with File in Git Index", "Open Working Tree Version"
    • staged pane: "Open Working Tree Version", "Remove from Git Index"
  • Double-click opening of commits in push result table
  • Synchronize View
    • "Mark as Merged"
    • "Open Merge Tool"
  • "Open Properties > Git" on Eclipse project now displays link to current HEAD
  • Repositories View
    • "Show In > Reflog" on repository nodes
    • Enable "Synchronize with Each Other" when two ref or tag nodes are selected

GitHub Mylyn Connector

Pull Request Support

  • Pull Requests can now be added as a Mylyn Task Repository type
  • The Pull Request task editor displays the commits and supports opening commits in the EGit commit viewer

Egit11-pull-request-editor.png

Import and Clone

  • Projects can now be cloned using the new Import > Git > Repositories from GitHub wizard
  • Projects cloned will appear in the Git Repositories view once the clone has completed

Egit11-github-clone-wizard.png

GitHub Java API

  • The GitHub Java API now supports the entire GitHub v3 API
  • The README is available here
    • Rendered version available here


Commits

EGit 1.1 - commits in gitweb

Back to the top