Closed hugovk closed 3 years ago
+1 on at least skipping archived repos. I just tried the tool and it quit after the 403 response from an archived repo in the org I was trying to update.
This is interesting because we set the repo type to public, which we would think would skip forks as forks is actually an option, but it's not doing that....https://pkg.go.dev/github.com/google/go-github/v32/github#RepositoryListByOrgOptions
So @halkeye added a PR to address this in #5. @halkeye can you take a look at this and see why forks are still showing up when public
is specified?
I'll take a look, I apologize for the delay, I was nursing a migraine all afternoon
https://developer.github.com/v3/repos/#parameters-1 doesn't seem to match actual https://docs.github.com/en/free-pro-team@latest/rest/reference/repos#list-organization-repositories
o.O so 'https://api.github.com/users/halkeye/repos?types=private' doesn't actually return my private repo, returns public repos
Okay, so I have code that handles public private and forks through 3 new flags But I can't figure out how to actually get private repos for a user.
This has been updated and is in v0.0.7.
When you say every repo, does it also apply topics/labels to forked and archived repos?
If so, can those be excluded by default? That is, only run on what GitHub calls "source" repos.
It's less likely people will want to get PRs to forks, and you can't PR an archived repo.
Thanks!