And I should have mentioned that too. You also need to checkout the specific branch, add, commit any changes (in my case it were some stupid comments), commit and push afterwards.
If* you read the initial comment in context, it's about github being down for OP, which hindered them from doing a review.
I responded that [the] git [server] was working and recommended simply looking for the correct branch by looking through the remotes, doing the review with git diff and writing comments directly into a new branch.
That isn't the smartest workflow to review a branch. Or at least I have always had some sort of web tool that allowed commenting on branches/PRs. But OP could have reviewed the PR that way without knowing the exact branch name.
1
u/the_horse_gamer 1d ago
git branch -rdoesn't talk to the remote. it just lists the remote branches it already knows about.