Re: updating github.com forks, developing in remote branches and svn:eol-style equiv?
- From
- Thomas Anderson <zelnaga@gmail.com>
- Date
- Mar 28, 2010, 17:07 UTC
- Message-ID
- <15b345f1003281007r3e8b3e86p787f9ef554054adf@mail.gmail.com>
- In-Reply-To
- <158811269761123@webmail102.yandex.ru>
On Sun, Mar 28, 2010 at 2:25 AM, Alexander Iljin <ajsoft@yandex.ru> wrote:
> You should do it the way you described - via local repository, because you > might need to resolve conflicts along the way. > There is the "Fork Queue" feature on GitHub, you may give it a try.
In playing around with their Fork Queue feature... I have a week old fork to which I've made no changes. I do "Select All" for al the changes in teh original fork and then select "Apply" in the drop down "Actions" menu. It then just sits there doing nothing. It says "Status: Processing 1 of 8 Commits" and that's it. Shouldn't it actually be doing something?
Show 5 quoted lines
> To have a local branch you should create it: > git checkout -b branchName remotes/origin/branchName > Remote branches are there only to track the state of the remote repo, > you should only commit to local branches and then push your work to > remotes.
I think I figured out some of my confusion - there's a "Create New Branch" checkbox in the "Checkout\Switch" dialog that needs to be checked that isn't by default. I guess the idea is that, by default, TortoiseGit assumes you want to make the branch you checkout the default branch?