Add git/github content (#6609)

* Added content to custom-validators topic

* Added contents to 10 git & github topics

* Apply suggestions from code review

styling clean up

* Added contents to 10 git and github topics

* Update src/data/roadmaps/git-github/content/committing-changes@2_z3R7seCvQVj-Na4H1SV.md

* Update src/data/roadmaps/git-github/content/creating-account@i7fIIHcBEk473te8bniJ5.md

* Update src/data/roadmaps/git-github/content/creating-branch@OegitQ5Ngjvd3ZfMpfrkM.md

* Update src/data/roadmaps/git-github/content/creating-repositories@c_FO6xMixrrMo6iisfsvl.md

* Update src/data/roadmaps/git-github/content/deleting-branch@1uDenoQ6zu7CT69FR2iQB.md

* Update src/data/roadmaps/git-github/content/fast-forward-vs-non-ff@agtPWS8j6i6wQPk10cy8E.md

* Update src/data/roadmaps/git-github/content/forking-vs-cloning@l1Wf7Pe_ah8ycCgslfSK4.md

* Update src/data/roadmaps/git-github/content/git-rebase@HMEfUFNu_Wp_Pac7VWHr-.md

* Added contents to 7 git and github topics

---------

Co-authored-by: dsh <daniel.s.holdsworth@gmail.com>
Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>

src/data/roadmaps/git-github/content/pull-requests@s3MzDYFPMASqiS8UnvWzW.md

@@ -1 +1,9 @@
 # Pull Requests
+
+A pull request is a proposal to merge a set of changes from one branch into another. In a pull request, collaborators can review and discuss the proposed set of changes before they integrate the changes into the main codebase. Pull requests display the differences, or diffs, between the content in the source branch and the content in the target branch.
+
+Visit the following resources to learn more:
+
+- [@official@Creating a pull request](https://docs.github.com/articles/creating-a-pull-request)
+- [@article@Pull Requests](https://www.atlassian.com/git/tutorials/making-a-pull-request#:~:text=In%20their%20simplest%20form%2C%20pull,request%20via%20their%20Bitbucket%20account.)
+- [@video@GitHub Pull Request in 100 Seconds ](https://youtu.be/8lGpZkjnkt4?si=qbCQ8Uvzn9GN2koL)

src/data/roadmaps/git-github/content/pushing--pulling-changes@ZVMCh9om37ee1qsecFa-N.md

@@ -1 +1,9 @@
 # Pushing / Pulling Changes
+
+When you pull changes in Git, you're fetching and integrating changes from a remote repository into your local repository. This operation updates your local branch with the latest changes from the remote branch. Whereas When you push changes in Git, you're sending your local commits to a remote repository, such as GitHub, GitLab, or Bitbucket. This operation updates the remote repository with your latest changes.
+
+Visit the following resources to learn more:
+
+- [@official@Pushing commits to a remote repository](https://docs.github.com/en/get-started/using-git/pushing-commits-to-a-remote-repository)
+- [@article@A Comprehensive Guide to git pull and git push](https://dev.to/alexmercedcoder/mastering-git-a-comprehensive-guide-to-git-pull-and-git-push-2eo3)
+- [@article@GIT Push and Pull Tutorial](https://www.datacamp.com/tutorial/git-push-pull)

src/data/roadmaps/git-github/content/pushing-tags@E3HAGNM-kXLL4Oci5JzpQ.md

@@ -1 +1,9 @@
 # Pushing Tags
+
+Pushing tags in Git is the process of sharing your local tags with a remote repository. Tags in Git are used to mark specific points in the repository's history, typically to signify a release or a milestone.
+
+Visit the following resources to learn more:
+
+- [@article@Tagging in git](https://git-scm.com/book/en/Git-Basics-Tagging)
+- [@article@How to Push Git Tags to Remote](https://kodekloud.com/blog/how-to-push-git-tags-to-remote/)
+- [@article@Git Push Tag to Remote Guide](https://phoenixnap.com/kb/git-push-tag)

src/data/roadmaps/git-github/content/reactions@XstmIysIi_lWo6RzszLBt.md

@@ -1 +1,7 @@
 # Reactions
+
+Reactions in GitHub are a way for users to express their feelings or opinions about issues, pull requests, comments, and other discussions without adding additional comments. They are similar to "likes" or "emojis" on social media platforms, providing a quick and non-verbal way to engage with content.
+
+Visit the following resources to learn more:
+
+- [@official@Add Reactions to Pull Requests, Issues, and Comments](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/)

src/data/roadmaps/git-github/content/rebase@99FVJ3Zs8n6lr8L95mG6g.md

@@ -1 +1,7 @@
 # Rebase
+
+Rebasing in Git is a powerful and potentially complex feature used to reorganize or modify a series of commits. The primary purpose of rebasing is to create a cleaner, more linear project history by moving or combining changes from one branch onto another.
+
+Visit the following resources to learn more:
+
+- [@official@Rebasing](https://git-scm.com/book/en/Git-Branching-Rebasing)

src/data/roadmaps/git-github/content/renaming-branch@_dPOVUbxApx0pfKPH8fgr.md

@@ -1 +1,8 @@
 # Renaming Branch
+
+Renaming a branch in Git means changing the name of a branch to something different while preserving its history and the commits it contains. The branch itself remains the same in terms of the code and history it tracks, but the reference (the name by which you refer to it) is updated
+
+Visit the following resources to learn more:
+
+- [@official@Renaming a branch - GitHub Docs](https://docs.github.com/github/administering-a-repository/renaming-a-branch)
+- [@article@Git Rename Branch – How to Change a Local Branch Name](https://www.freecodecamp.org/news/git-rename-branch-how-to-change-a-local-branch-name/)

src/data/roadmaps/git-github/content/squash@Z-srOhYFGVEKDexlJ6cjt.md

@@ -1 +1,9 @@
 # Squash
+
+Squashing in Git, refers to the process of combining multiple commits into a single commit. This is often done to create a cleaner and more concise commit history, especially before merging a feature branch into the main branch.
+
+Visit the following resources to learn more:
+
+- [@article@Git Squash Commits](https://www.freecodecamp.org/news/git-squash-commits/)
+- [@article@How to Squash Commits in Git](https://medium.com/iosnesia/how-to-squash-commits-in-git-e73a41248211)
+- [@video@GIT Tutorial - How to Squash Commits](https://youtu.be/viY1BbKZhSI?si=kORsEzQvCRFGauQa)