-
Hacktoberfest® is open to everyone in our global community. Whether you’re a developer, student learning to code, event host, or company of any size, you can help drive growth of open source and make positive contributions to an ever-growing community. All backgrounds and skill levels are encouraged to complete the challenge.
-
Hacktoberfest is a celebration open to everyone in our global community.
-
Pull requests can be made in any GitHub-hosted repositories/projects.
-
You can sign up anytime between October 1 and October 31.
To earn your Hacktoberfest tee or tree reward, you must register and make four valid pull requests (PRs) between October 1-31 (in any time zone). Pull requests can be made in any participating GitHub or GitLab hosted repository/project. Look for the 'hacktoberfest' topic to know if a repository/project is participating in Hacktoberfest. Pull requests must be approved by a maintainer of the repository/project to count. If a maintainer reports your pull request as spam or behavior not in line with the project’s code of conduct, you will be ineligible to participate. This year, the first 55,000 participants who successfully complete the challenge will be eligible to receive a prize.
Whether it’s your first or fiftieth pull request, there’s always more to learn! We’ve put together a few resources that can help you create quality pull requests, keep your repositories pristine, and build on your open source knowledge.
- Use any language.
- C, C++, JAVA, Data Structure and Algorithms.
- Go to the particular folder or (make a folder for your language if it doesnt pre-exist)
- Contribute only logical and Algorithm based solution.
- Problems of CodeChef, LeetCode, etc
Fork this repository and make changes in code as required. You can change it online or by cloning it in your device. Then Pust it on your Forked Repo for furteher Actions. Do not use special characters in the template above.
You have written some code in your branch, and are ready to commit. So, make sure to written good, clean commit messages. Let's review the anatomy of a commit message.
---
First line, no more than 50 characters
Details section, as long as you want. Not always necessary, but
available if you need it. Wrapped at 72 characters. Present imperative
tense is preferred for commits. That means "fix bug", not "fixes bug" or
"fixed bug".
- Use bullets if you need
- Bullets are a good way to summarize a few things
If you have too much info here, it might be a good candidate to break
down into multiple commits. You can use emoji here too :sparkles:
---
Go through the checklist on the pull request template to guarantee your submission is valid. Our team will review your application, approve and merge your submission if everything is correct. Otherwise, you will get notified of the changes requested in the pull request comment section.
Note: Don't Forget to add hacktoberfest-accepted Label.
Please check first and then send your codes with discription.
**All the best for the event **