Welcome to the GitHub Contribution Challenge Event at NIET!
This event is designed to enhance your GitHub skills while also giving you an opportunity to contribute to open source projects and compete with your peers. This README will serve as your roadmap to understand the general working of the GitHub challenge.
-
Introduction to GitHub Basics: Before diving into the challenge, the host/coordinator will provide a brief tutorial on the basics of GitHub, covering concepts such as forking, committing, and pull requests (PRs). This will ensure that all participants are equipped with the necessary knowledge to participate effectively.
-
Bug Fixing Challenge: In the main phase of the event, participants will be tasked with solving bugs in files within the provided repository. The repository will contain 10 files in each of the Python and Java languages, with the difficulty increasing with each file. Each file will be assigned certain points based on its difficulty level.
-
Scoring System: Participants will earn points based on the difficulty level of the files they successfully fix. The leaderboard will be shared in the WhatsApp Group in a few days after the event.
-
Submission Process: To participate, each participant must fork the repository, fix the bugs in the designated files, and submit a pull request (PR) for each fix. PRs will not be merged by the author of the repository to avoid conflicts between files.
NOTE: If you need help on how to submit refer here
- The repository contains 5 tasks representing increasing difficulty levels.
- Each task will consist of 2 files 1 Python & 1 Java. Participants can submit fixes for both the languages or any one of them.
- Participants are required to fix bugs in these files and submit separate PRs for each fix.
- Each successfully fixed file will earn the participant a certain number of points based on its difficulty level.
- The participant with the highest number of points at the end of the event will be declared the winner.
- Participants must adhere to the rules and guidelines provided by the host/coordinator throughout the event.
- Participants are encouraged to collaborate and help each other, but each participant must submit their own fixes via separate PRs.
- Code quality, clarity, and correctness will be taken into consideration during the evaluation process.
- Any attempts at cheating or plagiarism will result in disqualification from the event.
- Fork the repository to your GitHub account.
- Clone the forked repository to your local machine.
- Identify and fix bugs in the designated files within the repository.
- Commit your fixes and push them to your forked repository.
- Submit separate pull requests (PRs) for each fixed file.
- Training Phase: 45 Minutes
- Bug Fixing Phase: 75 Minutes
Nitish Kumar for all the Coding Problems
If you have any questions or need assistance during the event, feel free to reach out to the event organizers:
We hope you enjoy participating in the GitHub Contribution Challenge Event! This is a great opportunity to improve your GitHub skills, contribute to open source projects, and compete with your peers. If you have any questions or concerns, feel free to reach out to the event organizers.
Happy bug fixing, and may the best contributor win! 🏆