Codespace best practices

Switch branches instead of creating a new Codespace

Creating a new Codespace takes time and bandwidth.

To improve your workflow (especially when reviewing multiple pull requests (PRs)), switch branches in an existing Codespace instead of creating a new Codespace for each branch/PR on the same fork as follows:

1. Run git fetch to update the Codespace’s list of branches.
2. Run git branch -a to list all remote branches.
3. Run git switch <branchName> or git checkout <branchName> to switch to the branch you wish to review.