What You’ll Do: Teams will be required to: Work with Git and GitHub to complete assigned open-source tasks. Complete four different stations as part of the relay. Make genuine contributions to designated open-source repositories. Work on tasks such as documentation fixes, localization, testing, and bug reporting. Apply basic Git/GitHub and problem-solving skills. Submit their work for verification by station mentors. Move to the next station only after successfully completing the current one. Collaborate with teammates and divide tasks effectively. Work under time pressure while maintaining accuracy and quality. Complete all four stations and race to the finish line.
Team Event Team Size: 4–5 members
Registration Fee: ₹99 per team
Team Name: Required during registration
Team Leader: Required during registration Each team must work together throughout the challenge. Team composition must be finalized before the event day.
Eligibility & Requirements: Basic computer knowledge An active GitHub account Basic understanding of Git and GitHub A laptop with a functional code editor Basic problem-solving and troubleshooting skills Ability to work effectively as a team
Event Format: GitSetGo! will be conducted as a four-station competitive open-source relay race . Each station represents 25% of the overall challenge , making the total contribution of all four stations 100% .
Registration & Team Check-in: Teams will report to the venue and complete the required check-in process. Team names and members will be verified. Teams will receive their team ID and station route information.
Setup Check: Teams must ensure that their GitHub account is ready. The required repository must be forked where applicable. Participants should have their laptop, editor, and Git setup ready. A mentor will verify the team's setup before the race begins. Station 1 — 25%: Teams will receive their first open-source contribution task. Participants must understand the task, make the required changes, and submit their work for mentor verification. Once the task is successfully verified, the team can proceed to Station 2. Station 2 — 25%: Teams will face another open-source challenge requiring them to apply their Git/GitHub skills and build upon their progress. The contribution will be reviewed by the assigned mentor before the team can move forward. Station 3 — 25%: The challenge continues with another task designed to test the team's ability to solve problems and contribute effectively under time pressure. Teams must complete and verify their contribution before proceeding to the final station. Station 4 — 25%: The final station will test the team's ability to complete another open-source contribution accurately and efficiently. Successful verification at Station 4 marks the completion of the relay .
Venue
RV University
Bangalore, India
Live Leaderboard: Race Control may maintain a live leaderboard throughout the event. Team progress and completion times may be displayed as teams successfully complete their stations, adding a competitive element to the race.
Finish Line: A team's official time will stop once Station 4 has been successfully completed and verified . Teams will then report to Race Control to record their final completion time.
Post-Race Verification: Mentors may conduct a final quality check on submissions where required. Once all participating teams have completed their runs, the final rankings will be determined.
Judging & Ranking Criteria: Teams will be ranked primarily based on their total completion time , among teams that successfully complete and verify all four stations.
Rules & Guidelines: Each team must consist of 1-4 participants . Pre-registration is mandatory. Team composition must be finalized before the event. All tasks must be completed live during the event . Pre-written solutions, pre-prepared fixes, or work completed before the race are strictly prohibited. Standard developer tools such as editors, Git, linters, and official documentation are allowed. AI code-generation tools are not permitted for completing station tasks. Teams must attempt stations in the prescribed order: Station 1 → Station 2 → Station 3 → Station 4 . Teams may reattempt a rejected task, but the clock will continue running. Mentors may ask participants to explain their work to verify authenticity. Plagiarism, copied solutions, or assistance from another team may result in immediate disqualification . Teams must use only the repositories, task variants, and accounts assigned to them. Sharing solutions or task-specific assistance with other teams is strictly prohibited. The mentor's verification decision at each station is final. Participants must follow all instructions given by mentors, volunteers, and the organizing committee. Participants are expected to maintain professional and respectful conduct throughout the event.
Event: GitSetGo!
Domain: Open Source / Git / GitHub / Software
Development Format: Offline – Hands-on Relay