[GitHub] [lucenenet] NightOwl888 edited a comment on issue #447: Best way to setup dev machine for LuceneNet website edits

[GitBox <gi...@apache.org>]

NightOwl888 edited a comment on issue #447:
URL: https://github.com/apache/lucenenet/issues/447#issuecomment-808821253


   > [21-03-26 07:38:02.951]Info:BuildCommand.BuildCore.Build Document.Load.ConceptualDocumentProcessorFor git repo <C:/Users/Ron/source/repos/lucenenet>, can't find remote branch in this repo and fallback to use local branch [Documentation_work]: fatal: no upstream configured for branch 'Documentation_work'
   
   > I wonder if the reason the powershell script is complaining is because I named mine upstream rather then origin. I wonder that because the powershell script error said
   >
   > > can't find remote branch in this repo
   
   Okay, it sounds like you haven't configured a remote for your specific branch. Assuming you have `Documentation_work` checked out and you want to use the remote named `upstream`:
   
   ```
   git branch --set-upstream-to=upstream/Documentation_work
   ```
   
   Reference: https://stackoverflow.com/a/2286030
   
   Note it is possible to have a different remote and local name, but I have never done it because of the confusion it would cause me.
   
   I have no idea why the script would trigger that message, though. It doesn't seem to be doing anything with Git at all.
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org