Styjun

List of Python versions

Extract all GPU name, model and GPU ram

In predicate logic, does existential quantification (∃) include universal quantification (∀), i.e. can 'some' imply 'all'?

What is the logic behind the Maharil's explanation of why we don't say שעשה ניסים on Pesach?

First console to have temporary backward compatibility

How to react to hostile behavior from a senior developer?

Why are there no cargo aircraft with "flying wing" design?

Can I cast Passwall to drop an enemy into a 20-foot pit?

Novel: non-telepath helps overthrow rule by telepaths

Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

How discoverable are IPv6 addresses and AAAA names by potential attackers?

Identifying polygons that intersect with another layer using QGIS?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

Echoing a tail command produces unexpected output?

Apollo command module space walk?

What's the meaning of 間時肆拾貳 at a car parking sign

Ring Automorphisms that fix 1.

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

Can a non-EU citizen with residency visa traveling with me come with me through the EU passport line, when entering Schengen area?

Do I really need recursive chmod to restrict access to a folder?

How to override model in magento2?

How to find out what spells would be useless to a blind NPC spellcaster?

Why was the term "discrete" used in discrete logarithm?

Is there any way to checkout another branch readily in git?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

I'm working on a web project right now.
There are several branches; develop branch for debugging, feature branches for new features, etc.
The QA tester needs to test on both branches at the same time, so programmers have to switch branches when testers tell us to, and this is too bothering.
Is there any way to switch branches readily?

git

share|improve this question

asked Mar 22 at 9:01

shy111992shy111992

82

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  Try git worktree, git-scm.com/docs/git-worktree. It allows you to checkout multiple revisions to separated folders.
  
  – ElpieKay
  Mar 22 at 9:08
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  checkout multiple revisions to separated folders Thus trading disk space for speed and convenience of switching branches with cd instead of git checkout.
  
  – phd
  Mar 22 at 13:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  git worktree as @ElpieKay told you is the best way to do it. A shame he didn't propose it as an answer...
  
  – Philippe
  Mar 22 at 16:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'll try this. Thanks @ElpieKay !
  
  – shy111992
  Mar 25 at 6:01
  

  
  
  
  

add a comment | 

1

I'm working on a web project right now.
There are several branches; develop branch for debugging, feature branches for new features, etc.
The QA tester needs to test on both branches at the same time, so programmers have to switch branches when testers tell us to, and this is too bothering.
Is there any way to switch branches readily?

git

share|improve this question

asked Mar 22 at 9:01

shy111992shy111992

82

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  Try git worktree, git-scm.com/docs/git-worktree. It allows you to checkout multiple revisions to separated folders.
  
  – ElpieKay
  Mar 22 at 9:08
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  checkout multiple revisions to separated folders Thus trading disk space for speed and convenience of switching branches with cd instead of git checkout.
  
  – phd
  Mar 22 at 13:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  git worktree as @ElpieKay told you is the best way to do it. A shame he didn't propose it as an answer...
  
  – Philippe
  Mar 22 at 16:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'll try this. Thanks @ElpieKay !
  
  – shy111992
  Mar 25 at 6:01
  

  
  
  
  

add a comment | 

I'm working on a web project right now.
There are several branches; develop branch for debugging, feature branches for new features, etc.
The QA tester needs to test on both branches at the same time, so programmers have to switch branches when testers tell us to, and this is too bothering.
Is there any way to switch branches readily?

git

share|improve this question

asked Mar 22 at 9:01

shy111992shy111992

82

share|improve this question

asked Mar 22 at 9:01

shy111992shy111992

82

share|improve this question

asked Mar 22 at 9:01

shy111992shy111992

82

asked Mar 22 at 9:01

shy111992shy111992

82

asked Mar 22 at 9:01

shy111992shy111992

82

1 Answer
1

active

oldest

votes

1

To speed up working tree updating

As ElpieKay* and phd are suggesting in comments up above, a good way to avoid having to wait loading the whole working tree each time you need to check anything on another branch, is git worktree.

Basically, with :

git worktree add any/chosen/path

...you designate this given path as the base directory for an additional worktree, ready to host another branch, while another is checked out in your main tree. (not limited to two of course, check the linked above doc for all details)

---

To ease typing

In case you have to switch between two branches on a regular basis, one shortcut will be very convenient :

# check out the previously checked out branch
git checkout -

So when you switch back-and-forth between your 2 branches, at start you

git checkout feature
git checkout develop

and after that each git checkout - just toggles between the 2. (Bonus point for using just the "up" key once or a few times since you need the same line each time)

Let alone the fact that most users end up aliasing checkout to some one or two-letter variant, so that it's just the extremely short :

git co -

---

* (Hey ElpieKay, you deserve any rep** on this part of the answer, which is the most important, so write an answer and I'll erase the part, that's only fair)

** (...not to say that MUCH rep has been gained for now on this answer but still ;-)

share|improve this answer

edited Mar 25 at 23:48

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  For what it's worth, git worktree can also be a pain in the a**--it doesn't like having two worktrees point to the same branch. I find that disappointing in that it sometimes kills my workflow. YMMV. :-)
  
  – John Szakmeister
  Mar 26 at 0:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @JohnSzakmeister I agree. I never had a context in which the benefits (worktree updating times) actually meet or outweigh the costs (disk space and potential mistakes). But it could very well be that bigger repos give another ratio...
  
  – RomainValeri
  Mar 26 at 0:19
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55296093%2fis-there-any-way-to-checkout-another-branch-readily-in-git%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

1

To speed up working tree updating

As ElpieKay* and phd are suggesting in comments up above, a good way to avoid having to wait loading the whole working tree each time you need to check anything on another branch, is git worktree.

Basically, with :

git worktree add any/chosen/path

...you designate this given path as the base directory for an additional worktree, ready to host another branch, while another is checked out in your main tree. (not limited to two of course, check the linked above doc for all details)

---

To ease typing

In case you have to switch between two branches on a regular basis, one shortcut will be very convenient :

# check out the previously checked out branch
git checkout -

So when you switch back-and-forth between your 2 branches, at start you

git checkout feature
git checkout develop

and after that each git checkout - just toggles between the 2. (Bonus point for using just the "up" key once or a few times since you need the same line each time)

Let alone the fact that most users end up aliasing checkout to some one or two-letter variant, so that it's just the extremely short :

git co -

---

* (Hey ElpieKay, you deserve any rep** on this part of the answer, which is the most important, so write an answer and I'll erase the part, that's only fair)

** (...not to say that MUCH rep has been gained for now on this answer but still ;-)

share|improve this answer

edited Mar 25 at 23:48

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  For what it's worth, git worktree can also be a pain in the a**--it doesn't like having two worktrees point to the same branch. I find that disappointing in that it sometimes kills my workflow. YMMV. :-)
  
  – John Szakmeister
  Mar 26 at 0:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @JohnSzakmeister I agree. I never had a context in which the benefits (worktree updating times) actually meet or outweigh the costs (disk space and potential mistakes). But it could very well be that bigger repos give another ratio...
  
  – RomainValeri
  Mar 26 at 0:19
  

  
  
  
  

add a comment | 

1

To speed up working tree updating

As ElpieKay* and phd are suggesting in comments up above, a good way to avoid having to wait loading the whole working tree each time you need to check anything on another branch, is git worktree.

Basically, with :

git worktree add any/chosen/path

...you designate this given path as the base directory for an additional worktree, ready to host another branch, while another is checked out in your main tree. (not limited to two of course, check the linked above doc for all details)

---

To ease typing

In case you have to switch between two branches on a regular basis, one shortcut will be very convenient :

# check out the previously checked out branch
git checkout -

So when you switch back-and-forth between your 2 branches, at start you

git checkout feature
git checkout develop

and after that each git checkout - just toggles between the 2. (Bonus point for using just the "up" key once or a few times since you need the same line each time)

Let alone the fact that most users end up aliasing checkout to some one or two-letter variant, so that it's just the extremely short :

git co -

---

* (Hey ElpieKay, you deserve any rep** on this part of the answer, which is the most important, so write an answer and I'll erase the part, that's only fair)

** (...not to say that MUCH rep has been gained for now on this answer but still ;-)

share|improve this answer

edited Mar 25 at 23:48

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  For what it's worth, git worktree can also be a pain in the a**--it doesn't like having two worktrees point to the same branch. I find that disappointing in that it sometimes kills my workflow. YMMV. :-)
  
  – John Szakmeister
  Mar 26 at 0:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @JohnSzakmeister I agree. I never had a context in which the benefits (worktree updating times) actually meet or outweigh the costs (disk space and potential mistakes). But it could very well be that bigger repos give another ratio...
  
  – RomainValeri
  Mar 26 at 0:19
  

  
  
  
  

add a comment | 

To speed up working tree updating

As ElpieKay* and phd are suggesting in comments up above, a good way to avoid having to wait loading the whole working tree each time you need to check anything on another branch, is git worktree.

Basically, with :

git worktree add any/chosen/path

...you designate this given path as the base directory for an additional worktree, ready to host another branch, while another is checked out in your main tree. (not limited to two of course, check the linked above doc for all details)

---

To ease typing

In case you have to switch between two branches on a regular basis, one shortcut will be very convenient :

# check out the previously checked out branch
git checkout -

So when you switch back-and-forth between your 2 branches, at start you

git checkout feature
git checkout develop

and after that each git checkout - just toggles between the 2. (Bonus point for using just the "up" key once or a few times since you need the same line each time)

Let alone the fact that most users end up aliasing checkout to some one or two-letter variant, so that it's just the extremely short :

git co -

---

* (Hey ElpieKay, you deserve any rep** on this part of the answer, which is the most important, so write an answer and I'll erase the part, that's only fair)

** (...not to say that MUCH rep has been gained for now on this answer but still ;-)

share|improve this answer

edited Mar 25 at 23:48

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

git worktree add any/chosen/path

# check out the previously checked out branch
git checkout -

git checkout feature
git checkout develop

git co -

share|improve this answer

edited Mar 25 at 23:48

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335

answered Mar 22 at 9:14

RomainValeriRomainValeri

6,14321335