Welcome to Devsphere — a fast-paced, high-impact coding battleground where only your skills matter the most.

GDG Devsphere is a 3-hour individual participation event designed to challenge your development skills across multiple domains.

You’ll be given a curated sheet of 9 repositories:

• App Development (3)
• Web Development (3)
• FOSS (Open Source) (3)
• Machine Learning (3)

Each category includes:

• 🟢 Easy
• 🟡 Medium
• 🔴 Hard

Every difficulty carries different marks, so solve wisely and maximize your score!

Keep in mind, there is no step marking. It's either full or none.

• You will be given a document consisting 9 problems from different domains. You can attempt any number of questions.

• Each domain has 3 questions categorized as Easy, Medium and Hard, carrying marks accordingly.

• Fork the corresponding repository first and then clone it. Solve the problem in your local machine.

  1. Fork the repo
  • Click the Fork button at the top-right corner of the repository.
  
  2. Clone your forked repo
  • Click on <>Code and copy the HTTPS/SSH link.
  

  https://github.com/Google-Developers-Group-IIIT-Lucknow/{repo-name}.git

  git@github.com:Google-Developers-Group-IIIT-Lucknow/{repo-name}.git

  2. Then run in your local terminal:

  git clone git@github.com:Google-Developers-Group-IIIT-Lucknow/{repo-name}.git

• One-time setup — activate the pre-commit hook (run once inside the repo folder after cloning):

  git config core.hooksPath .hooks
  

  After this, every git commit will run the tests automatically and block the commit if they fail.

• When you are ready to commit your changes, the pre-commit hook will run the tests. You will be able to commit only when all checks pass.

  1. Stage the changes

  git add .
  

  or to stage a single file:

  git add path/to/file
  

  2. Commit changes

  git commit -m "your message here"
  

• Once, you are able to commit successfully, push your changes to your own fork.

  1. Push the changes

  git push origin {branch name}

• On your fork, there will be some more checks to validate your PR. In case, any of the checks fails, you will have to make changes, commit them and push again to re-run the workflow.

• Once the workflow succeed, you will be able to open your PR to the main repo of the problem.

Once, your PR opens successfully, you can see the leadboard updating with your username getting more marks as per the difficulty.

• AI tools are strictly prohibited → Immediate disqualification if detected
• Google is allowed