Welcome to my repository of solutions to various problems from GeeksforGeeks(GFG)!🎉
The solutions are neatly organized by difficulty and problem categories, making it easy to navigate and explore.
My GeeksforGeeks profile: RunarokHrafn
All problems in this repository are sourced from GeeksforGeeks. You can explore the problems here.
The upload of solutions to this repository was automated using a Chrome extension called GFG to GitHub. This extension streamlines the process of saving solutions to GitHub.
The Open Source Repository used for automation is available at GfG-To-GitHub.
Issues Faced & Trick to Find Missing Files 🛠️
During the automation process, I encountered an issue where the browser tab was closed too soon after solving a problem. As a result, only the README.md
file was created for some problems, but the corresponding code files were missing.
- Go to the repository directory: Navigate to GeeksForGeeks-solutions.
- Modify the URL: Change
hub
toingest
in the URL: gitingest.com/Runarok/GeeksForGeeks-solutions. - Manually check directory structure: Identify missing code files by excluding markdown files (
*md
). - Alternatively, ask ChatGPT: Paste the directory structure here, and I can help identify missing code files.
- Search browser history (CTRL + H): Look for the problem folder name (e.g., "Array Search").
- If history was cleared, visit GeeksforGeeks Explore to search for the respective problem.
- Copy the code: Go to the problem's page, copy the code, and manually upload it to the appropriate file in the respective folder.
└── Runarok-GeeksForGeeks-solutions/ └── Difficulty: Basic/ ├── Array Search/ │ └── README.md └── Array Subset/ ├── README.md └── array-subset.py
In this example:
- If the
array-search.py
file is missing, go to the GeeksforGeeks page for "Array Search", copy the code, and manually upload it to thearray-search.py
file in theArray Search/
directory.
Since GeeksforGeeks regularly adds new questions, my progress may not be fixed. Updates will be made as needed, but not on a fixed schedule.
Milestones / Completed Tasks Log 🏆
Date | Day | Topic / Category / Difficulty |
---|---|---|
24 JAN 2025 | Friday | Google tagged problems. |
Completed remaining problems from tags and sheets that were partially solved so far. | ||
30 JAN 2025 | Thursday | Hard Difficulty tagged problems. |
31 JAN 2025 | Friday | Linked List tagged problems. |
01 FEB 2025 | Saturday | SDE Sheet and Beginner's DSA Sheet. |
02 FEB 2025 | Sunday | Adobe tagged problems. |
03 FEB 2025 | Monday | Flipkart tagged problems. |
04 FEB 2025 | Tuesday | Samsung and Tree tagged problems. |
05 FEB 2025 | Wednesday | Graph and Two-pointer Algorithm tagged problems. |
06 FEB 2025 | Thursday | Stack and Binary Search tagged problems. |
07 FEB 2025 | Friday | Matrix tagged problems. |
08 FEB 2025 | Saturday | Love Babbar Sheet. |
09 FEB 2025 | Sunday | Accolite tagged problems. |
Free time ended here, so I began solving problems from here onwards. | ||
22 FEB 2025 | Saturday | Basic Difficulty tagged problems. |
27 FEB 2025 | Thursday | Microsoft and Amazon tagged problems. |
28 FEB 2025 | Friday | Strings and Arrays tagged problems. |
Finished all problems except those with testcase errors as of 2nd March |
I’m not doing this to create a portfolio or for external validation. I simply enjoy the satisfaction of completing something, similar to achieving 100% in a game. I also love coding and the learning process. My goal is to work through all the problems on GeeksforGeeks, improving my skills as I go. I focus on enjoying the journey and learning at my own pace rather than stressing myself out.
This repository idea was inspired by iamarghamallick's repository, whose solutions you can view here.
Got it! You want to update the GeeksForGeeks repository’s README to mention that you’ve created a new LeetCode solutions repository.
Here’s a well-written section you can add to the bottom of your GeeksForGeeks repository README.md
, to let visitors know about your new LeetCode project:
While this repository focuses on solving problems from GeeksForGeeks, I’ve also started working through problems on LeetCode.
Check it out here: Runarok/LeetSolutions