Xcode 7 doesn't show new remote branches using Git
In Xcode 7, after creating a new remote branch using Jira/Stash, when I pull master, the new branch used to show up as an optional origin branch. Now newer branches don't show up at all, so creating a new local branch isn't as easy.
Before you could go to Source Control > hover over your current working copy > select "Switch to Branch" and scroll to see the new origin/ branch. Once that was selected, Xcode automatically created a local branch.
Now I have to manually name/create a new branch locally and push it up (Create) the remote branch which can cause a lot of conflicts if you're working copy isn't master.
Is there a way to force Xcode to see all the remote branches via the Terminal, or by something I'm missing in Xcode?
ios xcode git jira
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
add a comment |
In Xcode 7, after creating a new remote branch using Jira/Stash, when I pull master, the new branch used to show up as an optional origin branch. Now newer branches don't show up at all, so creating a new local branch isn't as easy.
Before you could go to Source Control > hover over your current working copy > select "Switch to Branch" and scroll to see the new origin/ branch. Once that was selected, Xcode automatically created a local branch.
Now I have to manually name/create a new branch locally and push it up (Create) the remote branch which can cause a lot of conflicts if you're working copy isn't master.
Is there a way to force Xcode to see all the remote branches via the Terminal, or by something I'm missing in Xcode?
ios xcode git jira
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
1
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
1
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
2
my workaround is to drop into a terminal andgit pull
– mikebob
Nov 23 '15 at 16:29
add a comment |
In Xcode 7, after creating a new remote branch using Jira/Stash, when I pull master, the new branch used to show up as an optional origin branch. Now newer branches don't show up at all, so creating a new local branch isn't as easy.
Before you could go to Source Control > hover over your current working copy > select "Switch to Branch" and scroll to see the new origin/ branch. Once that was selected, Xcode automatically created a local branch.
Now I have to manually name/create a new branch locally and push it up (Create) the remote branch which can cause a lot of conflicts if you're working copy isn't master.
Is there a way to force Xcode to see all the remote branches via the Terminal, or by something I'm missing in Xcode?
ios xcode git jira
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
In Xcode 7, after creating a new remote branch using Jira/Stash, when I pull master, the new branch used to show up as an optional origin branch. Now newer branches don't show up at all, so creating a new local branch isn't as easy.
Before you could go to Source Control > hover over your current working copy > select "Switch to Branch" and scroll to see the new origin/ branch. Once that was selected, Xcode automatically created a local branch.
Now I have to manually name/create a new branch locally and push it up (Create) the remote branch which can cause a lot of conflicts if you're working copy isn't master.
Is there a way to force Xcode to see all the remote branches via the Terminal, or by something I'm missing in Xcode?
ios xcode git jira
ios xcode git jira
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
asked Nov 4 '15 at 16:55
whyozwhyoz
4,0803846
4,0803846
1
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
1
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
2
my workaround is to drop into a terminal andgit pull
– mikebob
Nov 23 '15 at 16:29
add a comment |
1
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
1
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
2
my workaround is to drop into a terminal andgit pull
– mikebob
Nov 23 '15 at 16:29
1
1
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
1
1
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
2
2
my workaround is to drop into a terminal and
git pull– mikebob
Nov 23 '15 at 16:29
my workaround is to drop into a terminal and
git pull– mikebob
Nov 23 '15 at 16:29
add a comment |
2 Answers
2
active
oldest
votes
Now you need to tick Fetch and Refresh Status
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
add a comment |
Ok, so as of Xcode 7.1.1, it looks like the way to do this is to:
1) Create your branch in Jira/Stash
2) In Xcode, go to Source Control
3) Select "Pull"
4) Click on the dropdown and you'll see the new "origin/..." branch
5) select the new branch and pull
6) go to Source Control, hover over your working copy, and select "Switch to Branch..."
7) find the new origin branch in the origin section and you'll create a new local branch
Some IDEs like Visual Studio may require you to pull "master" to get the new origin branches, but this seems to be the way it's done now in Xcode.
UPDATE: It appears I didn't have "Refresh server status automatically" checked which would eliminate most of these steps! (found in Xcode -> Preferences -> Source Control .. unless this was recently added in Xcode 7.3)
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f33527579%2fxcode-7-doesnt-show-new-remote-branches-using-git%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Now you need to tick Fetch and Refresh Status
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
add a comment |
Now you need to tick Fetch and Refresh Status
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
add a comment |
Now you need to tick Fetch and Refresh Status
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
Now you need to tick Fetch and Refresh Status
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
answered Nov 14 '18 at 15:17
Sh_KhanSh_Khan
42.7k51327
42.7k51327
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
add a comment |
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
1
1
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
Apple made it easier didn't they..thx for updating this! This is now the accepted answer
– whyoz
Nov 29 '18 at 6:11
add a comment |
Ok, so as of Xcode 7.1.1, it looks like the way to do this is to:
1) Create your branch in Jira/Stash
2) In Xcode, go to Source Control
3) Select "Pull"
4) Click on the dropdown and you'll see the new "origin/..." branch
5) select the new branch and pull
6) go to Source Control, hover over your working copy, and select "Switch to Branch..."
7) find the new origin branch in the origin section and you'll create a new local branch
Some IDEs like Visual Studio may require you to pull "master" to get the new origin branches, but this seems to be the way it's done now in Xcode.
UPDATE: It appears I didn't have "Refresh server status automatically" checked which would eliminate most of these steps! (found in Xcode -> Preferences -> Source Control .. unless this was recently added in Xcode 7.3)
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
add a comment |
Ok, so as of Xcode 7.1.1, it looks like the way to do this is to:
1) Create your branch in Jira/Stash
2) In Xcode, go to Source Control
3) Select "Pull"
4) Click on the dropdown and you'll see the new "origin/..." branch
5) select the new branch and pull
6) go to Source Control, hover over your working copy, and select "Switch to Branch..."
7) find the new origin branch in the origin section and you'll create a new local branch
Some IDEs like Visual Studio may require you to pull "master" to get the new origin branches, but this seems to be the way it's done now in Xcode.
UPDATE: It appears I didn't have "Refresh server status automatically" checked which would eliminate most of these steps! (found in Xcode -> Preferences -> Source Control .. unless this was recently added in Xcode 7.3)
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
add a comment |
Ok, so as of Xcode 7.1.1, it looks like the way to do this is to:
1) Create your branch in Jira/Stash
2) In Xcode, go to Source Control
3) Select "Pull"
4) Click on the dropdown and you'll see the new "origin/..." branch
5) select the new branch and pull
6) go to Source Control, hover over your working copy, and select "Switch to Branch..."
7) find the new origin branch in the origin section and you'll create a new local branch
Some IDEs like Visual Studio may require you to pull "master" to get the new origin branches, but this seems to be the way it's done now in Xcode.
UPDATE: It appears I didn't have "Refresh server status automatically" checked which would eliminate most of these steps! (found in Xcode -> Preferences -> Source Control .. unless this was recently added in Xcode 7.3)
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
Ok, so as of Xcode 7.1.1, it looks like the way to do this is to:
1) Create your branch in Jira/Stash
2) In Xcode, go to Source Control
3) Select "Pull"
4) Click on the dropdown and you'll see the new "origin/..." branch
5) select the new branch and pull
6) go to Source Control, hover over your working copy, and select "Switch to Branch..."
7) find the new origin branch in the origin section and you'll create a new local branch
Some IDEs like Visual Studio may require you to pull "master" to get the new origin branches, but this seems to be the way it's done now in Xcode.
UPDATE: It appears I didn't have "Refresh server status automatically" checked which would eliminate most of these steps! (found in Xcode -> Preferences -> Source Control .. unless this was recently added in Xcode 7.3)
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
edited Jul 5 '16 at 23:01
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
answered Nov 23 '15 at 20:29
whyozwhyoz
4,0803846
4,0803846
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
add a comment |
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
1
1
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
Thanks, this technique (pull) worked for me. But I enabled "Refresh server status automatically" and the list to switch to a branch still wasn't updating, so I don't know how reliable that is. Supposedly source control in Xcode 9 is vastly improved and is now integrated tightly with GitHub (they've been working with them directly). I hope so because git and Xcode have always had issues for me with every version of Xcode. We shall see.
– Ben Stahl
Jun 26 '17 at 18:39
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f33527579%2fxcode-7-doesnt-show-new-remote-branches-using-git%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
With Jira/Stash, why not use SourceTree? They go together. Forget about Xcode's git "support"; it's terrible.
– matt
Nov 4 '15 at 16:58
When you work with Android Studio, VS 2015 (TFS and Git), Xcode, Adobe Master Collection, and countless other UIs everyday, you just expect Apple to "figure it out" instead of having another window open in some dark corner of my Parallels...that's why...
– whyoz
Nov 5 '15 at 5:53
1
When you've tried to use Xcode's crappy source control interface for as long as I have - and given up every time - you don't expect Apple to figure it out.
– matt
Nov 5 '15 at 16:42
2
my workaround is to drop into a terminal and
git pull– mikebob
Nov 23 '15 at 16:29