Skip to content

Latest commit

 

History

History
39 lines (23 loc) · 1.71 KB

CONNTRIBUTING.md

File metadata and controls

39 lines (23 loc) · 1.71 KB

📢 Rules 😼 😼 😼:

✅ Pull requests can be submitted to any opted-in repository on GitHub or GitLab.

✅ The pull request must contain commits you made yourself.

✅ If a maintainer reports your pull request as 'spam' or 'invalid', it will not be counted toward your participation in Hacktoberfest.

✅ If a maintainer reports behaviour that’s not in line with the project’s code of conduct, you will be ineligible to participate.

✅ To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone. This year, the first 55,000 participants can earn a T-shirt.

What not to do ❗ ❗ 😤 😤 ❌ PRs that are automated (e.g. scripted opening PRs to remove whitespace/optimize images


❌ PRs that are disruptive (e.g. taking someone else’s branch/commits and making a PR)

❌ PRs that are regarded by a project maintainer as a hindrance vs. helping

❌ Something that’s clearly an attempt to simply +1 your PR count for October

PULL/MERGE REQUEST DETAILS HERE’S HOW WE VALIDATE CONTRIBUTOR PULL/MERGE REQUESTS (“PR/MRS”) FOR HACKTOBERFEST

[ OUT-OF-BOUNDS ] YOUR PR/MRS MUST BE WITHIN THE BOUNDS OF HACKTOBERFEST.

[ EXCLUDED ] REPOS THAT GO AGAINST HACKTOBERFEST’S VALUES WILL BE EXCLUDED FROM QUALIFICATION AND PR/MRS MADE TO THOSE REPOS WON’T COUNT.

[ SPAM ] YOUR PR/MRS MUST NOT BE SPAMMY.

[ PARTICIPATING ] YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR BE LABELED “HACKTOBERFEST-ACCEPTED.”

[ INVALID ] YOUR PR/MRS MUST NOT BE LABELED AS “INVALID”.

[ ACCEPTED ] YOUR PR/MRS MUST BE MERGED, HAVE THE “HACKTOBERFEST-ACCEPTED” LABEL, OR HAVE AN OVERALL APPROVING REVIEW.