CodeForge – The Open Innovation Gauntlet
Hosted on UnstopFetched 2 days ago
Friday, February 20, 2026
to Saturday, March 7, 2026
•
2 weeks long
Open SourceDevOpsWeb DevelopmentMobile DevelopmentInnovation
Student only
This hackathons is only open to students. Double check the event page for more information as this may mean only those from a particular university/country are eligible.
Event Type
in person
204
Participants
₹15,000
Prize Pool
18
Est. Projects
Organizers
Overview:
CodeForge is a team-based technical innovation challenge where participants will fork an existing open-source project and transform it into a production-ready, automated solution.
The competition evaluates engineering quality, innovation, DevOps implementation, and documentation standards.
Participants will work on provided base repositories and evolve them into scalable tools addressing real-world problems.
Event date: 7th March, 2026
Objective:
Enhance and extend an existing open-source codebase.
Integrate automation (CI/CD, containerization).
Demonstrate version-control discipline and documentation.
Deliver a functional prototype with a clear use case.
Eligibility:
Open to undergraduate and postgraduate students from any discipline with programming knowledge.
Inter-college teams: Allowed
Participants must have basic familiarity with Git, programming, and APIs.
Each participant can be part of only one team.
Number of Problem Statements:
3–5 base repositories provided
Each team receives one randomly assigned repository
Round 1 — Build & Automation Sprint:
Duration: 4 hours, Each team will receive one base repository (web app, API, or data project).
Teams must fork the repository and build a significantly enhanced version.
Tasks:
Add at least one innovative feature or improvement.
Integrate at least one open-source API/library.
Maintain structured commits and branching.
Provide documentation and README updates.
Mandatory Technical Requirements:
Containerized environment (Docker or equivalent).
CI/CD workflow (GitHub Actions or similar).
Unit testing or structured error handling.
Problem Statement: “How can you evolve this base project into a tool that solves a real-world problem or delivers a unique user experience?”
Presentation & Evaluation
Duration: 2 hours total (approx. 5–7 minutes per team)
Teams will present:
Problem statement and solution
Technical architecture
Automation pipeline
Demo and use case
Judging will evaluate:
Technical Implementation — 35%
Innovation & Problem Solving — 25%
DevOps & Automation — 25%
Documentation & Presentation — 15%
Rules:
Teams must work only on the repository assigned.
All commits must be made during the competition window.
Use of open-source libraries is permitted with attribution.
Plagiarism or copying another team’s work results in disqualification.
Judges’ decisions are final.
Late submissions will not be evaluated.
Submission Requirements:
GitHub repository link
Documentation
Demo/presentation