-
-
Notifications
You must be signed in to change notification settings - Fork 46.6k
Hacktoberfest flooded this repository with pull requests #3609
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
Comments
dear maintainers, if possible please check this issue out. |
We should have a GitHub Action that autocloses PRs that do not have tests. Criteria:
If both of those tests fail then the Action should autoclose the PR with a note pointing the contributor to CONTRIBUTING.md. |
Oh. I did not know that. Bye! Have a great day ahead. |
Sorry I've been a bit busy, lot of things going on. This seems like a good idea, I will get onto it. One more thing we should do is use labels extensively. This will give a short summary of what is happening in a given PR and it will become the first point of contact between a maintainer and a user.
|
No annotations (type hints). I believe that this would require |
Auto-labelling is a great idea, it highly simplifies the complete process of reviewing. |
I was also thinking about this #3239, Any suggestions? |
I see 10 open implementations for Problem 50 of Project Euler. My opinion is for |
@xcodz-dot There're some updates this year: https://hacktoberfest.digitalocean.com/hacktoberfest-update |
Ok, thanks for letting me know. I logged into hactoberfest on 1st October and the article was released on 3rd October |
Please also include unittest and perhaps pytest. doctest are not the most beautiful way to add test code: http://www.rohitschauhan.com/index.php/2018/07/05/python-relative-benefits-of-pytest-unittest-nose-and-doctest/#:~:text=Pytest%20provides%20essentially%20the%20same,very%20easy%20to%20do%20so. |
They are included in 2. above. Our automated testing uses pytest, not nose or unittest. Tests that follow pytest discovery rules will ensure that those PRs are not autoclosed. Doctests are not pretty but they are more simple for first-time contributors to understand. Contributors are free to chose either kind of test but we do not need to confuse contributors but explaining both. |
https://github.com/actions/stale |
This has already been implemented but the number of days before an issue becomes stale is 30 so it takes time to see the difference. |
You are right but we need a action for PR (stale is implemented for issues only), #3707. |
Um, no. https://github.com/TheAlgorithms/Python/blob/master/.github/workflows/stale.yml |
Whoops! thanks for letting me know. 😄 |
Is there any way we can help you with the pull requests ? |
Anyone can review any pull request on any repo on GitHub. Look at PRs that have passing tests and then near the top of the pull request click When you have had a good read through the changes, click the |
@xcodz-dot Please help me with my PR #3706 |
Hacktoberfest 2020 stats: started with 30 open PRs, ended with 521. |
I'd love to help up clear out the load of work!! |
Try suggesting changes, review PRs, mention maintainers (not me) if it is good to go. Thanks. |
On it. |
What is to be done to the pull requests whose authors have not followed the contribution guidelines and/or the code has invalid syntax? |
@mrmaxguns, you can suggest changes, write messages regarding their checklist |
Some stats regarding the Hacktoberfest: 🔢
|
This is troubling considering the contribution guidelines are very detailed. |
Oh, I do not agree. I think our high standards is what led to a lot of these PRs being considered spam. I see a ton of repos who take in any code without running any tests without requiring doctests, type hints, no plagerism. Those repos are useless but a ton of folks get free tee-shirts. I am really happy that we have high standards and that we do not dumb down our approach for Hacktoberfest. |
I agree. What I meant to say was that people should pay attention to the contribution guidelines before submitting a pull request so that it is easier for people to give them feedback. |
In a perfect world... |
That is why we are trying to set up a bot in this repository so that the bot takes care of the lower-level stuff for us to focus on the actual algorithm. :) |
Hi all, I have a question regarding PRs. Do we follow rule of 1 concept per PR sort of thing here or is it ok if a PR has multiple unrelated codes ? If we don't allow such PRs, do we have any flag to mark them so maintainers can reject those straight away? Thanks :) |
We have a label |
Another question, may sound dumb, but is there any documentation of labels we use, for example,
If there is no such documentation, I can add it to repo, let me know. Thanks :) |
Only members can add or update the labels. Thanks for the suggestion! |
According to the rate of PR Reviews, I think this might take upto 130 days to bring back numbers to near 10. |
Yeah but at least we will be prepared for the next Hacktoberfest. |
Possibly, If any of you guys could suggest them an idea |
I am sure that pull requests are getting closed beacause of stale rather than our reviews. Although that's good 😄 |
time to close this |
Yes. At least until 02 Oct. 2021. |
If possible can we all please focus on pull request and close the unnecessary ones
The text was updated successfully, but these errors were encountered: