scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
Challenge 1-21 by Sudhanshu
name: Sudhanshu Pandey github_user_name: sudhanshu-p
URL of fork: https://github.com/sudhanshu-p/scaler-september-open-source-challenge
Screenshot of cloned repo:
Successfully made a branch named sudhanshu-p-details.
The same branch on github:
Screenshot of changes on main:
Screenshot of changes on the new branch (sudhanshu-p-details):
Image of git reset used in challenge 9:
New branch, named new-details, copied from sudhanshu-p-details:
Screenshot of droping the stash files:
I also had a stashed commit earlier so I dropped that too.
Proof of raising merge conflict:
Proof of resolving merge conflict:
Solving the merge conflict:
Merge Conflict Solved:
PR:
In the challenge 17, I downloaded and installed github desktop, made a local repository, then pushed it to a new repo on remote. Further, I created a branch in the repository and made changes, then later made a PR and merged it successfully into main.
Link to that repo: https://github.com/sudhanshu-p/scaler-demo-repo
Screenshots:
Github Project TODO:
Using Git Alias
This is what I learnt about effective contribution to Open Source:
- Giving everything a clear name: As an open source contributor, you need to respect the value of the time of Open Source Maintainers. It is extremely critical to provide everything a clear description and document anything that needs to be done.
- It is ok if your code isn't 100% correct. But, you need to specify exactly what and how your code works, if there is anything special that needs to be done in order to do so, etc.
- DOCUMENTATION IS KEY!
Looking for an Open Source project to contribute to: Day#1:
- Went to the goodfirstissue website, started by searching for CSS and HTML issues since those were the ones I knew. Thought good of stop-analyzing-embed repo. Forked it, cloned it, but couldn't get it to run because of errors saying
npm ERR! While resolving: [email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@"^3.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/eslint-plugin@"2.x" from [email protected]
npm ERR! node_modules/eslint-config-react-app
npm ERR! dev eslint-config-react-app@"^5.2.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Then used --legacy-peer-deps took an hour, didn't work, then tried --force, also didn't work. Tried a few other solutions, none of them worked so moved to another repository.
- Saw a whole bunch of other projects, including one of my day-to-day websites lichess. Most of the projects were dead (No response to people requesting for assignment), or others were a bit too difficult to do.
So, right now I am still looking for projects I can contribute to with my knowledge.
Today was another day of trying different repositories to find some good issue that is of my capability to contribute. I searched for issues in multiple languages and came accross many repos which were just basic, would accept any contribution even if it's just adding your name to it, which I didn't want, I wanted my 1st open source contribution to be special, so I didn't do those. So I'm still looking for a repo which has some real life use and needs some contribution
Status update on the Open Source Contribution: Still looking for a repo that fits me.
Registration for hacktoberfest is done.
Status update on Open Source Contribution: Learning Scala because I love lichess and wanted to contribute to it! I know it's not a very good start, or even a start at all but I want it to be my 1st contribution.
Stuff learnt about Hacktoberfest:
- it is 1st come 1st serve, only the 1st 40k people win, which would be extremely difficult considering the scale of the event.
- Finding good repositories is KEY. You need to have a bunch of repositories already starred if you want to participate and win.
- Participation is fun. It's not about winning, it's about the experience.
Current status of Open Source contribution: Finished setup for Lila (Lichess developer environment) for my big contribution. Other than that, have created issues on a couple small repositories for web dev. Also looking for other opportunities.
Day 30! The 30 days are finally over! This felt so extremely long, I was learning something new, somethint I had heard before only in coding interview videos so easily. This challenge truly made me a git-pro. Now I understand why people add git to their resume as a skill. It really does mean a lot, and I'm sure there are still tons of features not yet discovered!
Thank you so much scaler, for not only providing the resources and the challenges, but also an incentive to keep me going, I believe that's what matters!
congrats you have completed milestone-4 successfully and you are good to go🎉