Bumping this very old topic because I wanted to start Beeminding GitHub activity but ran in to this same problem. My observations:
- I can’t see any reason that Beeminder should need write access to any repo.
- For public repos, it’s not even obvious why any user-specific API access is needed: in principle it ought to possible to beemind activity by username.
- I noted that GitHub invited me to request access to the organisation that owns some of the repos that I want to beemind. Were they private that might be an understandable necessity, but in any case I doubt that such a request would be approved under any circumstances, and a request for write access by an unknown external application should almost certainly be denied.
It would be great if the GitHub integration could be modernised, because at the moment this issue and another concerning beeminding commits on other branches are both blockers for my particular needs.
(Unfortunately multigitminder is probably not a suitable workaround for me, as it appears that it would be necessary to install it in each repo to be monitored, most of which are not my own personal repos.)