Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

contributors still limited when claiming issues when repository has a large number of contributors. #230

Open
laurynmm opened this issue Jul 7, 2023 · 0 comments

Comments

@laurynmm
Copy link

laurynmm commented Jul 7, 2023

In general, zulipbot limits new contributors to claiming one issue with the idea that once the contributor has a contribution successfully merged that the limit will be removed.

I think that the code in zulipbot used to check if a contributor has a merged contribution to a repository uses this GitHub API: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#list-repository-contributors.

And that response is limited to information on only the first 500 author email addresses ordered by number of commits:

To improve performance, only the first 500 author email addresses in the repository link to GitHub users. The rest will appear as anonymous contributors without associated GitHub user information.

Due to the number of contributors being well over 500 for the zulip/zulip repository (:tada:), this means that the limit of one issue won't be removed until the contributor has 3+ commits merged.

So it would be good to either find another way to check if the contributor has a merged commit in the repository for this check or maybe to adjust the zulipbot messages to be clear that the limitation to one issue will remain for their first few commits.

See relevant CZO conversation.


Current zulipbot message sent to contributors when limited to one issue.

Hello new contributor, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant