Open Samrat0505 opened 1 year ago
Screenshot showing the list of all the current branches inside of your forked clone repository:
Challenge #4 completed All contents of my local repository are now in sync with upstream
Challenge #5 Completed
Challenge #6 completed
Commit reflecting
Completed #7 Challenge
Git code:
Challenge #8 Completed
Challenge #9 Completed
Squash screenshot:
Challenge #10 Completed
Challenge #11 Completed
Challenge #12 Completed
Challenge #13 Completed
Challenge #14 completed Screenshot:
Completed #15 Challenge successfully
Completed #16 Challenge All Screenshots:
Completed #17 Challenge All Screenshot:
Completed #18 Challenge
Completed #19 Challenge It was a great experience for me to use the new thing on git hub through the program of Scaler Open Source September Challenge that is using Codespaces. It was a new learning for me, so I would like to thank whole scaler team for their initiative for making us learn new things in the form of challenges. I would also like to appreciate their program for 1 month git proficiency. While using the Codespaces today, the most interesting thing I found was the integration of the all things that is Command Prompt, code block , etc at one place so we need not to be worry about the changes etc at different tabs. Overall I would like to thank for the new learning and knowledge transferring to whole team.
Completed #20 Challenge It was a great experience for me to use the new thing on git hub through the program of Scaler Open Source September Challenge that is using Github Actions. It was a new learning for me, so I would like to thank whole scaler team for their initiative for making us learn new things in the form of challenges. I would also like to appreciate their program for 1 month git proficiency.
Completed #21 Challenge All Screenshot:
Completed #22 Challenge All Screenshot:
Completed #23 Challenge Screenshot:
Completed #24 Challenge
Here is the summary of what I have learnt so far in Open Source September Challenge:
Branch Name
Use group words: BUG -> to indicate the specific branch has work which fixes the bug. Use Bug ID to track the issue. ex: bug-123-fix
Use Hyphens and slashes to separate the different parts
Avoid using numbers only
Use short words and descriptive words
Pull Requests
Use Imperative tense: For commit messages and PR titles use imperative tense. ex: "Fix dashboard typo" instead of "fixed or fixes"
Use WIP: If you don't want to merge your work, but require early feedback on the code changes, name the PR with the word -WIP (Work In Progress) or In Progress
Give your PR a meaningful description
Show your functionality visually, whenever possible
Open Source Contribution
Visit opensource.creativecommons.org
Find the issues listed on the website that require community contribution
Issues available: Issues labelled Help Wanted are open for community contribution.
Issues Not available: Issues labelled "Staff Only" are unavailable for community contribution as the issue may require infra access.
Contribution Process: Once you have found the issue you like to work on, comment on it that you want to work on it. Start to code and submit the PR.
Follow the PR guidelines. Wait for the code review and address any issues raised as soon as you can.
Proposing a new Issue: Cannot find an issue to work on, create a new issue on the relevant repository including details about the implementation, and wait for feedback.
Challenge #25 Progress made: I have started exploring for open source projects and finding the projects where I would like to contribute or be able to contribute. But to be very honest, I am finding it difficult to find a project to contribute on. Since, I mentioned, I am a beginner, so searching a desired project is still very confusing for me. I am working on it and assure to provide a better result, Being overwhelmed by seeing the types of issues being raised in some of these projects. I am still eager to participate in open-source projects and I will keep searching for suitable opportunities. Overall, I would like to thank the whole scaler team for their tremendous way of teaching.
Challenge #26 Progress made: Today, also I have started exploring for open source projects and finding the projects where I would like to contribute or be able to contribute. But the result is same as the previous one. I have seen many YouTube videos to get an idea, how to select the project and to work on it. But more importantly I have adopted many things through this process. I have found many projects ideas to be made upon. So, in one way it giving me hope that I am not at a stage of void/null. Overall, again I would like to thank the whole scaler team for their tremendous way of teaching.
Completed #27 Challenge
Challenge #28 Progress made: Due to the participation in Smart India Hackathon 2023, I am unable to give my time on any platform. That result in breaking my streak of more than 100 days on LeetCode, GeekforGeeks etc. But, I will complete it soon. Overall, again I would like to thank the whole scaler team for their tremendous way of teaching.
Completed #29 Challenge Url Link of ReadMe: https://github.com/Samrat0505/Samrat0505/blob/main/README.md ScreenShot:
Completed #30 Challenge I have completed the google form and I have completed all the previous challenges on time. Thanks to this OpenSourceSeptemberChallenge by Scaler for making me learn and explore git.
name: Shreyansh Dubey github_user_name: Samrat0505 discord_id: shreyansh05_59319