🚀 ✨ Help beginners to contribute to open source projects.
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 open to everyone in our global community!
- Pull requests can be made in any GitHub-hosted repositories/projects.
- Sign up anytime between October 1 and October 31.
To qualify for the official limited edition Hacktoberfest shirt, you must register and make four pull requests (PRs) between October 1-31 (in any time zone). PRs can be made to any public repo on GitHub, not only the ones with issues labeled Hacktoberfest. 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 50,000 participants who successfully complete the challenge will earn a T-shirt.
Read more about participation details.
It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. I wanted to simplify the way new open-source contributors learn & contribute for the first time.
-
Edit this README.md file & append your information at the bottom of this file as follows:
- Name, Profession - Location
Example: 1. Kamalpreet Kaur, Student - Delhi, India
-
Commit the change to your fork, using a clear and descriptive commit message.
- Kamalpreet Kaur, Student - Delhi, India
- Hrishikesh Athalye, Student - Pune, India
-
If you wanted to offer more code changes to this repo you could edit/add any files/code and then follow a similar workflow.
-
You could alternatively look at any github's "Issues" tab. That is where people make requests to the public for your contributions aka "pull requests"
-
You can contribute anywhere. Sometimes repo maintainers are more receptive to pull requests than others. It often is recommended to make smaller changes and see how the maintainers respond to your requests. Ideally they merge in your changes, that is the point of a pull request, you are attempting to contribute to a larger project that you do not own.
When working with git with a world wide team you may be making changes at the same time someone else is, if you both change the same file there could be "merge conflicts". Remember to "git pull" or "git fetch" and resolve merge conflicts locally before attempting to create a "pull request".
- You can fork a project and compare across forks. Choose this option if you plan to contribute more than once.
- Or you can edit the original github repo's code directly. Choose this option if you have a quick contribution.