Projects STRLCPY git-open Commits cdfb1cb0
🤬
Revision indexing in progress... (symbol navigation in revisions will be accurate after indexed)
  • ■ ■ ■ ■ ■ ■
    README.md
    skipped 102 lines
    103 103  - Visual Studio Team Services
    104 104  - Team Foundation Server (on-premises)
    105 105   
    106  -### Configuration (GitLab support)
     106 +## Configuration
     107 + 
     108 +### Configuring the web destination (aka GitLab support)
    107 109   
    108 110  To configure GitLab support (or other unique hosting situations) you need to set some options.
    109 111   
    skipped 17 lines
    127 129  git config [--global] "open.https://git.internal.biz.protocol" "http"
    128 130  ```
    129 131   
    130  -### Default remote
     132 +### Configuring which remote to open
     133 + 
     134 +By default, `git open` opens the remote named `origin`. However, if your current branch is [remotely-tracking](https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches#_tracking_branches) a different remote, that tracked remote will be used.
    131 135   
    132  -Normally `git open` opens the remote named `origin`. When you fork a project
     136 +In some instances, you may want to override this behavior. When you fork a project
    133 137  and add a remote named `upstream` you often want that upstream to be opened
    134  -as the default remote. To accomplice this, you can do this:
     138 +rather than your fork. To accomplish this, you can set the `open.default.remote` within your project:
    135 139   
    136 140  ```sh
    137 141  git config open.default.remote upstream
    138 142  ```
     143 + 
     144 +This is equivalent to always typing `git open upstream`.
    139 145   
    140 146  ## Alternative projects
    141 147   
    skipped 65 lines
Please wait...
Page is in error, reload to recover