Re: IETF Git and GitHub tutorial

[Michael Richardson <[e-mail]>]

Salz, Rich <[e-mail]> wrote:
    >> And there is a serious limitation, which is that it pretty much
    >> impossible to rebase with only the web interface, so after having
    >submitted an edit, once it is accepted, one winds up with a tree (fork) you can not use again.
  
    > The work-around is simple and probably follows what most people do,
    > anyway: do not re-use a branch name for different items of
    > work. (Arguably that's an implied git best practice.) In fact, GitHub
    > pull requests use the branch name, so I would not be surprised if doing
    > this (which you shouldn't) can lead to problems anyway.

In order words, you have to know how to create a branch.
While helping some other newbies to git (who were on windows 10, and could
barely use a shell), when they use the crayon icon to edit/send-pull-request
it always forked to their account, and then used a branch "master".

At which point, we had no idea how to update what was in their account
without a shell.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [