Repo migration from github didnt seem to grab all PRs #1976

Comment

I just migrated https://codeberg.org/ClassClock/ClassClock from https://github.com/moralCode/ClassClock and noticed that, while the migration (with token) was seemingly successful, it seemed to miss all the currently-open PRs (mostly from dependabot) that are visible on github.

part of me wonders if this is a permissions issue with the token i provided (maybe i didnt give it permission for dependabot things? it DEFINITELY had PR read access though)

Wanted to raise it in case theres a better way to resolve this than "delete the repo and re-migrate it" - i dont care about the dependabot PRs as much as the one non-dependabot open PR

it seemed to miss all the currently-open PRs (mostly from dependabot) that are visible on github.

From my side there are no open PRs by dependabot on the github project (you should check the project page without being logged in).

It's likely that this is some special PR by Github - I don't think it can be accessed via the API and it's unlikely to be added to the migration tool as it's likely that it lacks information that a 'normal' PR has.

PEBCAK

The PR I wanted to see moved over (the python migration) was in https://codeberg.org/ClassClock/API/pulls..... Meaning it migrated correctly and I was looking at entirely the wrong repo when I reported this. I should have realized that a PR to update python in a repo thats mostly react code makes no sense...