Bug 345465 - Add option to checkout a particular SHA-1 commit
Summary: Add option to checkout a particular SHA-1 commit
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.12   Edit
Hardware: PC Linux-GTK
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2011-05-11 12:34 EDT by James Blackburn CLA
Modified: 2013-09-28 12:20 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Blackburn CLA 2011-05-11 12:34:18 EDT 
Eclipse EGit (Incubation)	0.12.1	org.eclipse.egit.feature.group
  Eclipse JGit (Incubation)	0.12.1	org.eclipse.jgit.feature.group

Team > Switch To ... Doesn't contain a 'Commit' option, though Compare With does.  In CVS we made tagged releases once a week (or more) leading to very many tags in the repo.  In git we can just annotate the release with a SHA-1.  It should be easy for someone to checkout a SHA-1 if they need to.
Comment 1 Matthias Sohn CLA 2012-02-28 19:35:24 EST 
I agree this would make sense.

As a workaround you may consider to use the "Open Git Commit..." command to lookup the commit for a given SHA1. This command can be configured into the workbench toolbar. Alternatively you may use "Search > Search > Git Search". These commands will open the commit in the commit viewer. You may use the checkout button in this view to checkout the commit.