Please avoid force-pushing to this PR. It makes it harder for reviewers to track what changed since the last review.

Just push new commits on top of the branch instead — PRs are squashed on merge, so the commit history doesn't need to be clean.

Not a bad idea, I like that the feature is somewhat compact and that it only requires one HTTP request (which should cache via CachedFunction for 1 hour by the way)

However I'm hesitant to add features for people who don't use Refined GitHub. Any reason why prevent-link-loss wasn't used?

Not a bad idea, I like that the feature is somewhat compact and that it only requires one HTTP request (which should cache via CachedFunction for 1 hour by the way)

However I'm hesitant to add features for people who don't use Refined GitHub. Any reason why prevent-link-loss2 wasn't used?

🤣

I'm glad of your suspicious. I use refined-github for so long that I don't remember when I started using it (maybe 7/8+ years ?). I tried to collaborate a couple of times, but usually some issues/PR were already proposed and not merged/closed (oh man, #5380 would be so nice! That helps me to sort which PR to review between meetings).

Well, for my test I used a temporary profile for development since I don't want to messup with the standard extension, it was just a quick feature to work on after the work.

google-chrome-stable \
  --user-data-dir=/tmp/potato \
  --load-extension=/home/patrick/git/patrick/refined-github/distribution

oh sorry, are you talking about this ?

I thought that was github alarming me that I posted a link from a link-from-review-commit-pr or something that would not work if someone reworks the PR. I was not aware that was a refined-github feature.

As for this feature, I'm thinking it should just show the current commit count instead. I've never seen a "next" button that includes the number of remaining pages in its label, so we should find a more common display. Appending "6 of 250 commit" after the buttons seems to be the easiest solution here.