Hacktoberfest '23 prelim results: 611 commits, 297 participants

[eshellman]

Wow! Thanks to all who helped and/or contributed. I'll post an issue/update when we've finished cleaning up.

As the repo has the hacktoberfest label, there's not need for PR's to also have that label!

We're proud of the many developers who've gotten their first taste of open-source contribution through free-programming-books and Hacktoberfest.

HOWEVER! We get a LOT of submissions during Hacktoberfest, so our review process does not get as much friendly helping care as it does during other months. Please have patience! There are a number of things you can do to facilitate efficient review and acceptance.

1. READ the CONTRIBUTING.md guidelines, and familiarize yourself with the existing content in the repo.
2. Check the linter results. If your PR has a red x beside it in the list of PRs, it means you need to fix it. We prioritize the review of PRs with green ✓s. Usually this is spacing or sorting.
3. Make atomic changes. It's much easier for us to review a PR that changes just one listing or a section of listing than a PR that makes several disparate changes. DO start each PR with a fresh branch!
4. If you get feedback on your PR, add commits to the PR instead of starting a new one. Please respect the work that reviewers do!
5. During October, we have an extra low tolerance for spammy PR's, including AI generated PR's, and these will be labelled as spam and/or get you banned.
6. Help others! Once you get familiar with our guidelines, you can contribute by explaining our policies.
7. To prioritize review, make sure your PR has an informative title.
8. Please respect the time of the reviewers. Once a PR has been reviewed, make changes on the same PR, so subsequent reviews can see what has be changed.

You don't need permission to work on something. Just do it.

Suggestions for things to work on:

• look at PRs and issues that have been automatically closed due to inactivity. Often the suggested changes are good but the submitter gave up for some reason. If you do pick up one of these, be sure to include the old PR or issue number in your new PR. It's polite, and it helps facilitate our review process.
• There are still many books whose authors are not including in the listing. We like to give them credit!
• Check links! this repo has been around long enough that resources have disappeared. Removing the dead links is just as important as adding new ones.
• New areas and languages tend to be thin on resources about them. But we don't like single-resource categories. Look for already-listed resources in growing fields that might benefit from being grouped together.

[saurabhprasadsah]

Hello sir I want to contribute this project Please assign me task.

[akshaybharwani]

Hello sir I want to contribute this project Please assign me task.

Kindly read the above comment? They have explained everything you need to know.

[saurabhprasadsah]

@akshaybharwani okay no issue.

[rajputpritesh1]

How to check my contribution is accepted or not?

[Suhanikashyap]

Hello , i Aldo want to contribute.

[eshellman]

Please be patient, there are more than 150 PRs being managed. But it won't help to add comments asking for review, as the PR's that have been waiting longest are at the top of the review queue. BUT if you have a red x next to your PR, it means that our linter bot has found a problem, and you should fix it! Similarly, if a conflict has developed, you should fix it.

[saurabhprasadsah]

Sure thanks @eshellman