Open snehalsenapati23 opened 2 years ago
URL :- https://github.com/snehalsenapati23/scaler-september-open-source-challenge Below is the screenshot cloned project.
Screenshot of the list of all the current branches inside of my forked clone repository:
Screenshot showing the latest repository contents:
challenge 9: Before-
Removed the 8th-challenge commit-
After-
Challenge 10:
Challenge 11 Done:
Challenge 13 Done:
Challenge 14: Resolving Merge Conflicts
Challenge 16 Done:-
Challenge 17: Done Demo Repo link - https://github.com/snehalsenapati23/Demo-github-desktop
Downloaded Github-Desktop
Created new branch snehal-new
Added a new line in new branch
commited and created new PR
All commits in new branch snehal-new
All commits in main branch
Merged both
Challenge 20 Done:
2.challenge 20 In Progress column
3.challenge 20 in Done column project link-https://github.com/users/snehalsenapati23/projects/2
Challenge-21 : Screenshot 1
Screenshot of using alias:
Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️
Challenge 23:
1 -The important branches in any project is the -Main Stable version -Development -Where all the changes take place -QA - Where all the testing takes place 2 -The branches we will be working on has to be named as per a standard. For example, the branch name can include words like bug, fix, WIP, etc, the issue it will be solving, author name, etc. 3 -The name of these branches should match with the naming convention of the rest of the team.
1 -The pull request created should be descriptive of the problem that is being solved. 2 -It should refer to the issue which the pull request closes. 3 -The pull request should be created from a feature branch of the forked repo and not the main. 4 -The changes should be reviewed and tested before creating pull request.
1-Always see for good-first-issue in the repos 2-Avoid long descriptive names 3-Create only meaningful issues
Currently looking for issues that I am able to contribute. I explored many issues and side by side upgrading my hands on the tech stack but most people had listed complex issues that are, as of now, beyond my contributing knowledge. I will soon update this when I find a suitable issue to contribute.
-Found a beginner open-source project to create a pull request and update the HTML file. Forked Repository Link Pull request of contribution -PR got approved and merged .
Github page- link
Registered in Hacktoberfest
congrats you have completed milestone-3 successfully and you are good to go🎉
I had assigned with two issues but one issue is successfully merged and another is not.
I will try to correct this.
Ideas that I liked and upvoted are:
Day1-Day30 challenge Successfully learned and completed each task. Scaler Open Source Challenge is when I started my open-source journey. I enjoyed and learned a lot about open source from this 30 days challenge. I think if I had tried to learn individually myself I didn't have learned so many things as I learned from this 30 days challenge. I'll be looking forward to participating in Hacktoberfest and also contributing to more open-source projects. The scaler discord community has also helped me a lot and I am so happy to discover and be a part of the Scaler Discord community! Special thanks to @shivaylamba for adding such great tasks to the challenge, and thanks to @kuraakhilesh8230 and the other Scaler Stars for guiding me. We need more events like this on web dev as well.
congrats you have completed milestone-4 successfully and you are good to go🎉
name: Snehal Senapati github_user_name: snehalsenapati23