r3
is considered obsolete and r2
is the latest revision -- I believe that should get things unstuck.
Hey. Is there a way to "see myself out" out of a discussion thread in Reviewable? I commented on a thread in a long-running PR, and every day there is a new comment there, and it pops up in my "things to look at", even though I really don't want to look at it anymore.
I know it's a bad idea to have long-running PRs, but we have them from time to time.
TypeError: s.$ref.transaction is not a function Try again.
FF 103.0 on Ubuntu 20, private window, no extensions. Any suggestions?
Failed to update your list of reviews: Error: GitHub error 403 on POST https://api.github.com/graphql: You have exceeded a secondary rate limit. Please wait a few minutes before you try again. Note that the review list refreshes automatically, so you don't need to reload the page manually. Try again.
Failed to update your list of reviews: Error: GitHub error 502 on POST https://api.github.com/graphql: Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include
BFEA:38C1:139041:4204FB:62F54A60when reporting this issue. Try again.
@pkaminski I have noticed a weird issue: in some PRs source code does not get displayed (a spinner spins over every file in the PR). This persists after multiple refreshes.
I had a look at network panel, and haven't found any activity to fetch source code. Metadata (repository, labels, users, members etc) are fetched from GH properly.
The PR where I see it right now is https://reviewable.io/reviews/ridge/tectonic/16879
My browser is FF 106.0, and I'm under Linux/x86-64.
import
line. Is there a way to ignore changes that, say, match a certain regular expression?
I use stacked pull requests (no special tooling currently, I know there’s stuff like spr
out there), i.e. I often have a chain of PRs where the bases are set so that A merges into main, B merges into A, C merges into B, etc.
My understanding[1] is that github is supposed to automatically retarget the dependent PRs, so e.g. if I merge “A”, the merge base for “B” would be set to main. But if I use “merge & delete” in reviewable to merge A into main, github seems to instead close the A<-B pull request. Any idea how to fix this?
[1] https://github.blog/changelog/2020-05-19-pull-request-retargeting/