aboutsummaryrefslogtreecommitdiff
path: root/git-codereview/review.go
diff options
context:
space:
mode:
authorShulhan <m.shulhan@gmail.com>2024-07-21 03:48:32 +0700
committerShulhan <m.shulhan@gmail.com>2026-04-09 22:20:06 +0700
commit31f678e5a420fecf567c30bc66e40b43ad85fd17 (patch)
treee3b1a4b83fb4db9e2dde3d3846966240e3b5e618 /git-codereview/review.go
parent99962d5770bded6aa8fac22d4c74103b5f832d6d (diff)
downloadgo-x-review-main.tar.xz
git-codereview: support remote other than "origin"HEADmain
For the git-codereview commands to works on any Go's repositories, the remote name for "origin" must be pointed to the Go original repository URL (in most cases the one with go.googlesource.com domain). The problem is when the "origin" is from the fork, all of the git-codereview commands then will not works. For example, in computer X, I clone the this repository from "https://go.googlesource.com/review" (the origin) and then push my changes on "git@git.sr.ht:~shulhan/go-x-review" (the fork). In another computer Y, I then clone from the fork to continue my works. The fork become origin. One of the solution is to rename the remote names manually each time we clone the fork. The only cons using this solution is every time new branch created we need to remember to pass "--set-upstream" during git push. This changes introduce "remote" configuration in codereview.cfg. When one first working on fork of Go repository, they set the "remote" key, commit it, and push it. When they cloned the fork, they did not needs to changes anything except adding new remote using the pre-defined name. Change-Id: I335d08fd8b7efe17ba07b3c0a3794f9ccf59b339
Diffstat (limited to 'git-codereview/review.go')
0 files changed, 0 insertions, 0 deletions