Open Sambhav250703 opened 2 years ago
1.URL of your forked repository : https://github.com/Sambhav250703/scaler-september-open-source-challenge
Screenshot showing the list of all the current branches inside of your forked clone repository
Here is the screenshot of my latest repository contents
Screenshot for challenge 9 :-
Screenshot of new branch
Challenge 13
Good to go verified ✅
Challenge 14 :-
Challenge 16 :- Resolve this merge conflict using local git
Challenge 17 : Repository link : https://github.com/Sambhav250703/Sambhav2612
2.Create a new repository in github
3.Added my name in README file
4.Published repo on remote
6.Create new file
7.Publish to Github
Open a Pull request pull request link : https://github.com/Sambhav250703/Sambhav2612/pull/1
Pull origin
Challenge 20: Repo link: https://github.com/Sambhav250703/Sambhav25
Board link : https://github.com/users/Sambhav250703/projects/1/views/1
Challenge 20: Repo link: https://github.com/Sambhav250703/Sambhav25
Board link : https://github.com/users/Sambhav250703/projects/1/views/1
Do challenge 20 correctly and attach screen shots of all the files of your project which should show done after moving from inprogress
Challenge 21 :
Updated changes in challenge 20 : Repository link : https://github.com/Sambhav250703/Sambhav25 Project link : https://github.com/users/Sambhav250703/projects/1/views/1
Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️
Challenge 23 : Here is a summary of what I discovered after reading those articles:
Branches:- -Any project's main/master, default, and stable branches are its most crucial divisions. -Development: A branch that is kept apart from the main branch and where all updates are made. -All testing is conducted in QA. -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.
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:- -Writing appropriate commit messages and PR descriptions is crucial. -Appropriate naming should be utilised. -Before delegating to others, we should check our PR. They ought to have descriptive titles.
Challenge 24
Finally I have been assigned to three issues :
**Challenge 25 :**
**Update Challenge 25 :**
Update Challenge 25 :
Challenge 26 :-
Registered for Hacktoberfest -2022
Contributor of a Open source Project Repo with Scaler Discord Members.
congrats you have completed the milestone-3 successfully and you are good to go🎉
Challenge 27 Hacktoberfest 2022 has the following sections where you can contribute:
Code contributions Non-Code contributions
Tips:
You can search the #hacktoberfest topic on GitHub and filter by programming language.
Most of us face problem to find a good first issue which is also a part of Hacktoberfest 2022, I've created a customised link by which you can find a good first issue: Click here to search good first issue I've created a Notion template to manage our Open Source contributions. You can duplicate the template and use it for Hacktoberfest 2022 as well as in any of your further Open Source contributions You can tract your Hacktoberfest 2022 progress here Hacktoberfest rules: [ OUT OF BONUS ] YOUR PR/MRS MUST BE WITHIN THE BOUNDS OF HACKTOBERFEST.
[ EXCLUDED ] REPOS THAT GO AGAINST HACKTOBERFEST’S VALUES WILL BE EXCLUDED FROM QUALIFICATION AND PR/MRS MADE TO THOSE REPOS WON’T COUNT.
[ SPAM ] YOUR PR/MRS MUST NOT BE SPAMMY.
[ PARTICIPATING ] YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR BE LABELED “HACKTOBERFEST-ACCEPTED.”
[ INVALID ] YOUR PR/MRS MUST NOT BE LABELED AS “INVALID”.
[ ACCEPTED ] YOUR PR/MRS MUST BE MERGED, HAVE THE “HACKTOBERFEST-ACCEPTED” LABEL, OR HAVE AN OVERALL APPROVING REVIEW.
ONCE YOUR PR/MRS PASS ALL THE CHECKS ABOVE, IT WILL BE ACCEPTED FOR HACKTOBERFEST AFTER THE 7-DAY REVIEW PERIOD.
Contributions I made till now in the challenge:
[ ] Updating HTML File [ ] - Palindrome.py [ ] - Bubble sort algorithm [ ] - Add name in contributors list [ ] - First contribution in hello open source
**Challenge 29 :**
Upvoted ideas :
My Project idea discussion links :
Challenge 30: I have learnt a lot about git and GitHub through this challenges. It boosted my confidence a lot . Looking forward for more challenges like this.
congrats you have completed milestone-4 successfully and you are good to go🎉
name : Sambhav Jha github_user_name: Sambhav250703