Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358474 - [client][status] Link from git-status to git-clone
Summary: [client][status] Link from git-status to git-clone
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4 RC1   Edit
Assignee: Susan McCourt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 14:30 EDT by John J. Barton CLA
Modified: 2012-02-08 16:51 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John J. Barton CLA 2011-09-21 14:30:33 EDT
Often as soon as I commit and push, I want to merge then switch back to my dev branch. I believe this a common workflow.

Currently I have to go to the repository link, drill down on my project, checkout other branch, then merge.

Better would be link from the git-status page to the git-clone page open on the branch I just pushed.

Best would be if the git-status page offered checkout+merge for other branches just when I finished, ie when my list of unstaged/staged files was complete.
Comment 1 Tomasz Zarna CLA 2011-09-22 08:08:47 EDT
(In reply to comment #0)
> Often as soon as I commit and push, I want to merge then switch back to my dev
> branch. I believe this a common workflow.

Just to clear up, is that what would you do in the console (assuming you're on master)?

git commit ...; git push origin master:master; git merge dev; git checkout dev

What are the changes you have just pushed? Are they merged from the dev branch?

What I usually do with my opened dev branches, is after I pushed some changes I rebase all of them (with master). Have you tried that?
Comment 2 Susan McCourt CLA 2012-02-07 13:30:55 EST
I may be able to solve this generically with "related pages"
Comment 3 Susan McCourt CLA 2012-02-08 16:51:17 EST
fixed with a new command "go to repository" in the git plugin.
Then a "related links" contribution for the command.

This surfaces in several ways:

- the "related pages" menu contains "Repository" when you are a Git Status page (the original request), Git Log page, or the navigator (if the nav root is in a git repo)
- also, from the nav objects you can select a folder and choose "Git Repository"