<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Thanks Max! That was very enlightening. One more question…</div><div><br>On 29 Mar 2017, at 19:57, Max Moiseev <<a href="mailto:moiseev@apple.com">moiseev@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div class="">[...]</div></div></blockquote><blockquote type="cite"><div><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><div>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><br></div><div>Best regards</div><div>Pavol Vaskovic </div></body></html>