snapshot of https://github.com/zulip/zulip.git @ 48c69911c7dd4e03b20552eb3bd77ad8151c1357 (2026-09-15)

docs/git/collaborate.md

@@ -0,0 +1,59 @@
+# Collaborate
+
+## Fetch another contributor's branch
+
+What happens when you would like to collaborate with another contributor and
+they have work-in-progress on their own fork of Zulip? No problem! Just add
+their fork as a remote and pull their changes.
+
+```console
+$ git remote add <username> https://github.com/<username>/zulip.git
+$ git fetch <username>
+```
+
+Now you can check out their branch just like you would any other. You can name
+the branch anything you want, but using both the username and branch name will
+help you keep things organized.
+
+```console
+$ git checkout -b <username>/<branchname>
+```
+
+You can choose to rename the branch if you prefer:
+
+```bash
+git checkout -b <custombranchname> <username>/<branchname>
+```
+
+## Check out a pull request locally
+
+Just as you can check out any user's branch locally, you can also check out any
+pull request locally. GitHub provides a special syntax
+([details][github-help-co-pr-locally]) for this since pull requests are
+specific to GitHub rather than Git.
+
+First, fetch and create a branch for the pull request, replacing _ID_ and
+_BRANCHNAME_ with the ID of the pull request and your desired branch name:
+
+```console
+$ git fetch upstream pull/ID/head:BRANCHNAME
+```
+
+Now switch to the branch:
+
+```console
+$ git checkout BRANCHNAME
+```
+
+Now you work on this branch as you would any other.
+
+Note: you can use the scripts provided in the tools/ directory to fetch pull
+requests. You can read more about what they do [here][tools-pr].
+
+```bash
+tools/fetch-rebase-pull-request <PR-number>
+tools/fetch-pull-request <PR-number>
+```
+
+[github-help-co-pr-locally]: https://help.github.com/en/articles/checking-out-pull-requests-locally
+[tools-pr]: zulip-tools.md#fetch-a-pull-request-and-rebase