Challenge-1, 2, 3, 4, 9, 11, 13, 14, 16, 17, 20, 21, 23, 24, 25, 26, 27, 28, 29 and 30 done

[rahulsrivastava1]

name: Rahul Srivastava github_user_name: rahulsrivastava1

[rahulsrivastava1]

URL of forked repository: https://github.com/rahulsrivastava1/scaler-september-open-source-challenge Screenshot:

[rahulsrivastava1]

[rahulsrivastava1]

[rahulsrivastava1]

challenge 9 done :)

[rahulsrivastava1]

Challenge 11:-

[rahulsrivastava1]

Challenge 13 :- Stash command

[rahulsrivastava1]

Git Merge Conflicts

[rahulsrivastava1]

Challenge 16

[rahulsrivastava1]

Challenge 17 - Exploring GitHub Desktop

[rahulsrivastava1]

Challenge 20

[rahulsrivastava1]

Challenge 21 :- Creating Alias

[kuraakhilesh8230]

Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️

[rahulsrivastava1]

Challenge 23

Summarizing what I have learnt about contributing to open sources effectively:

Issues

• We can find issues relevant to our interests by using label, which also help us to know if the issue is something we can work on.
• If we want to make some changes not specified in any issues, we have to create an issue stating what we want to change by giving a proper description.
• The issue must clearly state the purpose of its creation

Branches

• 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.
• 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.
• The name of these branches should match with the naming convention of the rest of the team.

Pull requests

• The pull request created should be descriptive of the problem that is being solved.
• It should refer to the issue which the pull request closes.
• The pull request should be created from a feature branch of the forked repo and not the main.
• The changes should be reviewed and tested before creating pull request.

[rahulsrivastava1]

Challenge 24

---

• Went through the repositories from Link

• Issue was open to fix the UI.Link

• Forked the repository and started working on it.

• Almost I have solved the fixed of UI but still I feel it should be more optimal.

• Hope so author will like it and by tomorrow the issue will be close and my work will be appreciated.

• I have made the changes and still working on it...

[rahulsrivastava1]

Challenge 25

---

1. Talking about the yesterday's topic, I worked on the UI that was assigned by the author after I requested him.
2. Then work further on issue
3. Luckily, he liked my approach and merged into his repository.
4. My work you can check by clicking this Link
5. Attaching the Ss so you can check more.

[rahulsrivastava1]

Challenge 26

---

[rahulsrivastava1]

Day 27

---

Well, I had completed my registration for Hacktoberfest yesterday.

Below are the special points which I liked for Hacktoberfest 2022 :-

• Code Contributions
• Non-Code Contributions

Also found these points, which I thought very remarkable:

Only check repository which are having #hacktoberfest tag . Need to merge 4 pull/merge request and wait for confirmation. The PR will take 14 days to verify. If all 4 PRs will be accepted then congratulations, we are having our Schwags!!!! Now is the correct time now to start searching for the repositories with Hacktoberfest tag.

[rahulsrivastava1]

Challenge 28

---

My one PR successfully merged to this repository. and, right now I am planning to work on this issue in this repository. I have commented on the issue and waiting to assign myself.

[rahulsrivastava1]

Challenge 29

---

[rahulsrivastava1]

Challenge 30

---

Today, is the day of one of the best Scaler program i.e., Open Source September, where I have learned lots of new things in Git. Earlier, I know how to clone the repository, Init the project, and then commit and then push etc. as I needed that time. But, today I can say that I have acquired lots of new commands of git. Like Squash, then rebase command etc.

In this a month journey, many members helped me whenever I have stucked on any task so a big Thank You to them.

I will looking forward to implement my yesterdays idea in Scaler GitHub repository.

And, also looking for new challenges.

[Mrjoy832]

Milestone-4 done ✅