<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 29, 2017, at 11:06 AM, Pavol Vaskovic <<a href="mailto:pali@pali.sk" class="">pali@pali.sk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""></div><div class="">Thanks Max! That was very enlightening. One more question…</div><div class=""><br class="">On 29 Mar 2017, at 19:57, Max Moiseev <<a href="mailto:moiseev@apple.com" class="">moiseev@apple.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div class="">[...]</div></div></blockquote><blockquote type="cite" class=""><div class=""><div class="">cd swift</div><div class="">git checkout master</div><div class="">utils/update-checkout --scheme=master</div><div class="">git checkout -b my-new-branch</div><div class="">... some work gets done …</div><div class="">git add .</div><div class="">git commit -m “Adding an absolutely awesome new feature”</div><div class="">git push mine my-new-branch # please note that I prefer to call my personal fork ‘mine’ whereas usually people call their fork remotes ‘origin’ and the upstream ‘upstream’.</div><div class="">open <a href="https://github.com/apple/swift" class="">https://github.com/apple/swift</a></div></div></blockquote><br class=""><div class="">When/where/how did you switch from upstream to your own fork (after the initial update-checkout)? Or am I misunderstanding how that works?</div></div></div></blockquote><div>You don’t need to switch from one remote to the other. It is only a matter of where you get the updates from and push your changes to. Typically you would pull from the upstream (apple/swift) and push changes to origin (yourown/swift).</div><div><br class=""></div><div>update-checkout script will call `git pull origin BRANCH_NAME` so, I guess my unusual approach to naming remotes works well in this case.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class=""><br class=""></div><div class="">Best regards</div><div class="">Pavol Vaskovic </div></div></div></blockquote></div><br class=""></body></html>