You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2021/03/27 21:13:57 UTC

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

NightOwl888 commented on issue #447:
URL: https://github.com/apache/lucenenet/issues/447#issuecomment-808803182


   Remotes are local references to remote repositories. They exist in the local configuration of your copy of the repository.
   
   You can view a list of all of the remotes by using the command
   
   ```
   git remote
   ```
   
   Or, even better, you can see the URLs of the remotes
   
   ```
   git remote -v
   ```
   
   Do note it is possible to set up a remote to pull from one repo and push to another (hence the 2 entries for each remote name).
   
   But the bottom line is, if a remote already exists in your local repository that maps it to a remote one, there is no need to add it again. From that point, you can use its name.
   
   > Do note using remotes is only a shortcut to make commands simpler - you could just as well use URLs to specify which repository to push to, fetch from, or pull from.
   >
   > Also, a remote exists at the top level of the repository, so you can use it for any number of branches.


-- 
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