scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
scaleracademy
Challenge 1 to 30
name: Nayana Pralhad Pardhekar github_user_name: nayanapardhekar
URL of your forked repository: https://github.com/nayanapardhekar/scaler-september-open-source-challenge/tree/main
A screenshot of the cloned project in your system:
Challenge 3
Screenshot showing the list of all the current branches inside of your forked clone repository
Challenge 17
- Download Git Desktop
- Created new Repository as DEsktop-Demo
- Added and Edited README.md file
- Publish Repo
- Created new branch as NayanaP
- Push and Created a Pull Request
- Created and Merged Pull Request
- Repository Link: - https://github.com/nayanapardhekar/DEsktop-Demo
Challenge 20
-
Repo Link: - https://github.com/nayanapardhekar/ToDoBlog
-
Project Link: - https://github.com/users/nayanapardhekar/projects/1/views/1
Challenge 20
- Repo Link: - https://github.com/nayanapardhekar/ToDoBlog
- Project Link: - https://github.com/users/nayanapardhekar/projects/1/views/1
not done challenge-20 correctly do it asap
Challenge 22
- GitHub Repo : - https://github.com/nayanapardhekar/New-Portfolio
- GitHub Page : - https://nayanapardhekar.github.io/New-Portfolio/Index.html
Challenge 20
- Repo Link: - https://github.com/nayanapardhekar/ToDoBlog
- Project Link: - https://github.com/users/nayanapardhekar/projects/1/views/1
not done challenge-20 correctly do it asap
Can you please tell where I have mistaken, What should I correct?
congrats you have completed the milestone-2 successfully and you are good to go🎉
Challenge 23 : Here I present the summary of that I got to learn from the given sources.
About Branches:
- Categories:
- Regular Git Branches: Development (dev), Master (master) and QA (QA)
- Temporary Git Branches: Bug Fix, Hot Fix, Feature Branches, Experimental Branches and WIP branches.
- These branches should be named in accordance with the team's overall naming scheme. Words like "bug fix," "WIP," "the issue it will solve," "author name," and other similar phrases can be used in the branch name.
- Any project's main/master, default, and stable branches are its most crucial divisions.
Issues:-
- Using labels can help us find problems that are relevant to our interests and assess whether or not we can take action to solve the issue.
- If there are changes we wish to make that aren't covered by any existing issues, we must create a new issue and specify the changes in it.
- For someone new to open source, excellent-first-issues labels are often a fantastic place to start
Pull Request
- The pull request created should be descriptive of the problem that is being solved.
- Link PR to the issue if you are solving one.
- Review changes before creating a pull request.
Contribution Process
- Identify issue to work on basis on given guidelines, and comment on it to avoid conflicts.
- Write code and submit PR. PR should follow guidleines.
- Wait for code review and address any issues raised as soon as you can.
Challenge 24 :
Found two beginner opensource projects to create a pull request and updating the file.
1st project
- Forked Project : - https://github.com/nayanapardhekar/Contribute-To-This-Project
- Contributed to it and made a pull request : - https://github.com/Syknapse/Contribute-To-This-Project/pull/1685
2st project
- Forked Project : - https://github.com/nayanapardhekar/hello-open-source
- Contributed to it and made a pull request : - https://github.com/mazipan/hello-open-source/pull/520
Challenge 25:
In last Challenge 24 I had contributed to 2 opensource / beginner projects and send a pull request. Among which one pull request has been merged successfully that is:
- PR got approved - https://github.com/Syknapse/Contribute-To-This-Project/pull/1685
- Changes appeared here in live webpage - https://syknapse.github.io/Contribute-To-This-Project/
The 2nd PR is yet to be merged. Till then still on the search of new beginner or suitable issue for me to contribute to.
Challenge 26:
- My 2nd contribution from Challenge 24 got merged today. Still in search for new issues suitable for me.
PR got Approved : https://github.com/mazipan/hello-open-source/pull/520
Challenge 27:
What is Hacktoberfest?
- Hacktoberfest is a month-long, community-wide celebration of open source software. It is run by DigitalOcean alongside partners like GitHub and Twilio.
- To participate, you must make four valid pull requests submitted to public GitHub repositories. On top of a boost to your open-source cred, participants are rewarded with prizes, like stickers, T-shirts, or a new plant-a-tree alternative.
Rules for participating?
- To win a prize, you must make at least four pull requests (PRs) between October 1 and October 31.
- Your pull requests must contain commits you made yourself.
- Pull requests reported by as spam will be marked as invalid and won’t count.
- Pull requests can be made to any public repository on GitHub.
- Pull requests must have been merged, approved, or labelled as hacktoberfest-accepted.
- You will be ineligible to participate if you break rules of conduct, leave spammy PRs, or fail to follow quality standards.
You can join the Hacktoberfest discord server to connect with the community and network with other open-source enthusiasts, ask questions and find projects. click the link to navigate to the server.
Challenge 28:
Overall Contributions I had made during this challenge: -
- https://github.com/mazipan/hello-open-source/pull/520
- https://github.com/Syknapse/Contribute-To-This-Project/pull/1685
- https://github.com/jatinkumar027/Nourishing-Skills/pull/14
- https://github.com/firstcontributions/first-contributions/pull/55121
Challenge 29:
Ideas upvoted :
- https://github.com/scaleracademy/open-source-projects/discussions/155
- https://github.com/scaleracademy/open-source-projects/discussions/148
- https://github.com/scaleracademy/open-source-projects/discussions/63
My idea:
- https://github.com/scaleracademy/open-source-projects/discussions/156
Challenge 30: Finally it's an end for this splendid event. It was an super interactive event containing combination of smooth and hard challenges daily. Being a part of this challenge was such a good choice as we got to learn a lot in detail about Git and GitHub. Some challenges were actually so out of box which made us explore GitHub more out of our comfort zone and spice up the things and following them were the no-sweat challenges which used to calm us down. Overall it was a great experience on this month long challenge and would definitely looking forward further for such events by scaler.
