First-contributions: Add documentation on why use of branches is encouraged

[Roshanjossey]

🐞 Problem
One question I get often is why contributors should create branches to push their code.

🎯 Goal

Provide users a better understanding of how branching helps workflow in GitHub

💡 Possible solutions

We don't wanna bloat the main tutorial. This can be added to https://github.com/firstcontributions/first-contributions/blob/master/additional-material

📋 Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes.
Submit a pull request and add this in comments - Addresses #
Ask for a review in comments section of pull request.
Celebrate your contribution to this project. 🎉

[Trshant]

hi @Roshanjossey , i'd like to at least start on this one. i am not very experienced in git, but i have something to contribute.

[Roshanjossey]

@Trshant, sure. Go ahead.

You could learn about this while you're writing this up.

[Trshant]

@Roshanjossey , Please have a look.

[ishakaranwal18]

Can I start working on this....?

[gordongab]

Hey, can I help to add to this as well? I think it would be a good learning tool for myself and others.

[digitaldina]

12690 above pull request solves this

[phaniChidella]

I am working on this now. I will add a text which answers the question "why contributors should create branches to push their code".

[phaniChidella]

13170 contains my changes.

[radiantly]

Please close this issue as #13170 addresses it.

[krishnatangirala]

@Roshanjossey I am assuming this issue is still open to contribution?

[Roshanjossey]

@krishnatangirala, No.

We have received multiple pull requests to address this issue. We are yet to merge one and close this issue.

[krishnatangirala]

@krishnatangirala, No.

We have received multiple pull requests to address this issue. We are yet to merge one and close this issue.

Thanks @Roshanjossey That's helpful to know

[akshatra]

In open-source community, branches are actually repository forks, so that project maintainers can lock down access to the master repository and can acquire integration through pull requests. This makes life much easier for the maintainers.
Also it becomes easier for the developers to revert back to their previous changes and contributors to make changes without actually affecting the master branch.
Thus the concept of making branches becomes very essential in version control environments like GitHub.
Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a branch, which ensures that the master branch only contains finished and approved work.

Pull requests can only be opened if there are differences between your branch and the upstream branch. You can specify which branch you'd like to merge your changes into when you create your pull request.

[jeffrey-hui]

Kindly remove the help wanted tag to filter this out of the other issues that need help! :)

@krishnatangirala, No.
We have received multiple pull requests to address this issue. We are yet to merge one and close this issue.

Thanks @Roshanjossey That's helpful to know

[LoganMugane]

Could i work on this?

[jhasaurabh312]

@Roshanjossey is this issue still open for contribution?

[jhasaurabh312]

@Roshanjossey I have committed the code and sent a pr for the issue #11007.
Please go through the changes.

[ajeyprasand]

can I start working on this?
since I am a beginner I need to explore more!!!

[silent-devil]

branches contains the modification done by you while if we use the master copy then modification will be done in original program which will disturb the original program

[ucalyptus]

@Roshanjossey merge this already?

[DXTkastb]

I have tried to explain branching with the help of an example.