Skip to content
This repository has been archived by the owner on Mar 14, 2023. It is now read-only.

Highfive is welcoming existing contributors as new #38

Closed
jdm opened this issue Jan 17, 2015 · 6 comments
Closed

Highfive is welcoming existing contributors as new #38

jdm opened this issue Jan 17, 2015 · 6 comments

Comments

@jdm
Copy link
Contributor

jdm commented Jan 17, 2015

A workaround would be to use per_page=10000 instead.

@jdm
Copy link
Contributor Author

jdm commented Jan 18, 2015

I lied, there's still a Link header containing

<https://api.github.com/repositories/724712/contributors?page=2>; rel="next", <https://api.github.com/repositories/724712/contributors?page=27>; rel="last"

so I'm not sure why highfive is greeting long-time contributors.

@nrc nrc changed the title Github contributors API doesn't provide a next link anymore Highfive is welcoming existing contributors as new Jan 19, 2015
@nrc
Copy link
Member

nrc commented Jan 20, 2015

This seems to be limited to a few users - @Aatch and 'Yurumu' (that isn't in fact a GitHub user, so not sure exactly who is having the problem). In @Aatch's case, the problem seems to be that he is not on the list of contributors for Rust. That seems to be a GitHub bug, not ours.

We could probably maintain a list of people who are known contributors to a repo and check that list as well as the contributors list from GitHub. In fact, that would save us an API call in many cases, so we could add contributors who are on the GitHub list too. Although this is a bit of a hack, it is better than annoying regular contributors.

@jdm
Copy link
Contributor Author

jdm commented Jan 20, 2015

Yurume == @lifthrasiir

@Aatch
Copy link

Aatch commented Jan 20, 2015

@nick29581 how about using a local database of contributors that gets populated as highfive sees new contributors? If they're not in that list, add them and then make the call to see if they're in the contributor list. Basically just maintain your own database of contributors and use Github to fill in the gaps.

@nrc
Copy link
Member

nrc commented Jan 20, 2015

I hope I have fixed this, at least for @Aatch and @lifthrisir, by adding a contributors section to the json file for a repo. We could extend this by adding all contributors and only checking the API when that fails, or we could maintain our own DB to do pretty much the same thing.

@nrc
Copy link
Member

nrc commented Jan 20, 2015

Closing in favour of #41, please re-open if my fix did not in fact fix things

@nrc nrc closed this as completed Jan 20, 2015
nrc added a commit that referenced this issue Jan 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants