Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when cycling through changed files #439

Closed
bolt12 opened this issue Oct 23, 2023 · 2 comments
Closed

Error when cycling through changed files #439

bolt12 opened this issue Oct 23, 2023 · 2 comments

Comments

@bolt12
Copy link

bolt12 commented Oct 23, 2023

Issue Description

Type: bug report

Describe what happened (or what feature you want)

When reviewing a PR and cycling through changed files with [q or ]q I get an error for some particular files.

Before pressing ]q:
image

after:

image

Describe what you expected to happen

It should go to the next changed file without an error

How to reproduce it (as minimally and precisely as possible)

  1. review: Fix Peer Sharing issue #4642 IntersectMBO/ouroboros-network#4644
  2. cycle through changed files
  3. error
@Danthewaann
Copy link
Contributor

I have the same problem. I've found that running git diff manually with the commit range that octo uses for the commit to review returns an error like so:

$ git diff a6ca7c6..fa4aef9
fatal: ambiguous argument 'a6ca7c6..fa4aef9': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

So this is likely what is causing your problem too.

@Danthewaann
Copy link
Contributor

Actually I think I now what the problem is.

After just running git pull locally and then re-running :Octo review commit and selecting the commit that was failing before it now successfully views it without throwing up any error.

So you need to make sure your local copy of the PR branch is up to date with the remote one it seems.

@bolt12 bolt12 closed this as completed May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants