diff --git a/src/data/roadmaps/git-github/content/committing-changes@2_z3R7seCvQVj-Na4H1SV.md b/src/data/roadmaps/git-github/content/committing-changes@2_z3R7seCvQVj-Na4H1SV.md index 2a5a169a1..4033a1991 100644 --- a/src/data/roadmaps/git-github/content/committing-changes@2_z3R7seCvQVj-Na4H1SV.md +++ b/src/data/roadmaps/git-github/content/committing-changes@2_z3R7seCvQVj-Na4H1SV.md @@ -5,4 +5,4 @@ Committing changes in Git is a crucial part of version control, allowing you to Visit the following resources to learn more: - [@official@How git commit works](https://github.com/git-guides/git-commit) -- [@article@Git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) \ No newline at end of file +- [@article@Git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) diff --git a/src/data/roadmaps/git-github/content/creating-account@i7fIIHcBEk473te8bniJ5.md b/src/data/roadmaps/git-github/content/creating-account@i7fIIHcBEk473te8bniJ5.md index 2c1eaf559..24cb75609 100644 --- a/src/data/roadmaps/git-github/content/creating-account@i7fIIHcBEk473te8bniJ5.md +++ b/src/data/roadmaps/git-github/content/creating-account@i7fIIHcBEk473te8bniJ5.md @@ -4,4 +4,4 @@ To get started with GitHub, you'll need to create a free personal account on Git Visit the following resources to learn more: -- [@official@Creating an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) \ No newline at end of file +- [@official@Creating an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) diff --git a/src/data/roadmaps/git-github/content/creating-branch@OegitQ5Ngjvd3ZfMpfrkM.md b/src/data/roadmaps/git-github/content/creating-branch@OegitQ5Ngjvd3ZfMpfrkM.md index 289b0ecdd..61e19c5c7 100644 --- a/src/data/roadmaps/git-github/content/creating-branch@OegitQ5Ngjvd3ZfMpfrkM.md +++ b/src/data/roadmaps/git-github/content/creating-branch@OegitQ5Ngjvd3ZfMpfrkM.md @@ -5,4 +5,4 @@ Creating a branch in Git is a fundamental part of working with version control, Visit the following resources to learn more: - [@official@Git branch documentation](https://git-scm.com/docs/git-branch) -- [@article@Git branch](https://www.atlassian.com/git/tutorials/using-branches) \ No newline at end of file +- [@article@Git branch](https://www.atlassian.com/git/tutorials/using-branches) diff --git a/src/data/roadmaps/git-github/content/creating-repositories@c_FO6xMixrrMo6iisfsvl.md b/src/data/roadmaps/git-github/content/creating-repositories@c_FO6xMixrrMo6iisfsvl.md index 56f4966be..ed9f24690 100644 --- a/src/data/roadmaps/git-github/content/creating-repositories@c_FO6xMixrrMo6iisfsvl.md +++ b/src/data/roadmaps/git-github/content/creating-repositories@c_FO6xMixrrMo6iisfsvl.md @@ -4,4 +4,4 @@ Creating a Git repository means setting up a system to track changes in your pro Visit the following resources to learn more: -- [@official@Quickstart for repositories - GitHub Docs](https://docs.github.com/en/repositories/creating-and-managing-repositories/quickstart-for-repositories) \ No newline at end of file +- [@official@Quickstart for repositories - GitHub Docs](https://docs.github.com/en/repositories/creating-and-managing-repositories/quickstart-for-repositories) diff --git a/src/data/roadmaps/git-github/content/deleting-branch@1uDenoQ6zu7CT69FR2iQB.md b/src/data/roadmaps/git-github/content/deleting-branch@1uDenoQ6zu7CT69FR2iQB.md index 3f8d7c516..3cf1eeced 100644 --- a/src/data/roadmaps/git-github/content/deleting-branch@1uDenoQ6zu7CT69FR2iQB.md +++ b/src/data/roadmaps/git-github/content/deleting-branch@1uDenoQ6zu7CT69FR2iQB.md @@ -5,4 +5,4 @@ Deleting a Git branch means removing a line of development from your Git reposit Visit the following resources to learn more: - [@official@Creating and deleting branches within your repository](https://docs.github.com/articles/creating-and-deleting-branches-within-your-repository) -- [@article@How to Delete a Git Branch Both Locally and Remotely](https://www.freecodecamp.org/news/how-to-delete-a-git-branch-both-locally-and-remotely/) \ No newline at end of file +- [@article@How to Delete a Git Branch Both Locally and Remotely](https://www.freecodecamp.org/news/how-to-delete-a-git-branch-both-locally-and-remotely/) diff --git a/src/data/roadmaps/git-github/content/fast-forward-vs-non-ff@agtPWS8j6i6wQPk10cy8E.md b/src/data/roadmaps/git-github/content/fast-forward-vs-non-ff@agtPWS8j6i6wQPk10cy8E.md index 79779d8f2..dc9e1a719 100644 --- a/src/data/roadmaps/git-github/content/fast-forward-vs-non-ff@agtPWS8j6i6wQPk10cy8E.md +++ b/src/data/roadmaps/git-github/content/fast-forward-vs-non-ff@agtPWS8j6i6wQPk10cy8E.md @@ -13,4 +13,4 @@ Visit the following resources to learn more: - [@article@Git Merge: To Squash Or Fast-Forward?](https://dev.to/trpricesoftware/git-merge-to-squash-or-fast-forward-3791) - [@article@Difference between a git fast forward and no fast forward](https://gist.github.com/moraisaugusto/1fa02c49b6d9833fcdf665505595ac2e) - [@video@GIT Fast Forward Visualized](https://youtu.be/DN1fNYoJgDw?si=_TZKACj4SCOuESGm) -- [@video@git merge no fast forward](https://youtu.be/X_8atqzsO8U?si=e9hMQg_aWLRMWf4O) \ No newline at end of file +- [@video@git merge no fast forward](https://youtu.be/X_8atqzsO8U?si=e9hMQg_aWLRMWf4O) diff --git a/src/data/roadmaps/git-github/content/pull-requests@s3MzDYFPMASqiS8UnvWzW.md b/src/data/roadmaps/git-github/content/pull-requests@s3MzDYFPMASqiS8UnvWzW.md index a0d01e5f6..34c89c744 100644 --- a/src/data/roadmaps/git-github/content/pull-requests@s3MzDYFPMASqiS8UnvWzW.md +++ b/src/data/roadmaps/git-github/content/pull-requests@s3MzDYFPMASqiS8UnvWzW.md @@ -1 +1,9 @@ -# Pull Requests \ No newline at end of file +# 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) \ No newline at end of file diff --git a/src/data/roadmaps/git-github/content/pushing--pulling-changes@ZVMCh9om37ee1qsecFa-N.md b/src/data/roadmaps/git-github/content/pushing--pulling-changes@ZVMCh9om37ee1qsecFa-N.md index 3f315aac8..eee7e88e4 100644 --- a/src/data/roadmaps/git-github/content/pushing--pulling-changes@ZVMCh9om37ee1qsecFa-N.md +++ b/src/data/roadmaps/git-github/content/pushing--pulling-changes@ZVMCh9om37ee1qsecFa-N.md @@ -1 +1,9 @@ -# Pushing / Pulling Changes \ No newline at end of file +# 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) \ No newline at end of file diff --git a/src/data/roadmaps/git-github/content/pushing-tags@E3HAGNM-kXLL4Oci5JzpQ.md b/src/data/roadmaps/git-github/content/pushing-tags@E3HAGNM-kXLL4Oci5JzpQ.md index fc053c88e..7998bccc0 100644 --- a/src/data/roadmaps/git-github/content/pushing-tags@E3HAGNM-kXLL4Oci5JzpQ.md +++ b/src/data/roadmaps/git-github/content/pushing-tags@E3HAGNM-kXLL4Oci5JzpQ.md @@ -1 +1,9 @@ -# Pushing Tags \ No newline at end of file +# 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) \ No newline at end of file diff --git a/src/data/roadmaps/git-github/content/reactions@XstmIysIi_lWo6RzszLBt.md b/src/data/roadmaps/git-github/content/reactions@XstmIysIi_lWo6RzszLBt.md index 45f975fe9..592e02873 100644 --- a/src/data/roadmaps/git-github/content/reactions@XstmIysIi_lWo6RzszLBt.md +++ b/src/data/roadmaps/git-github/content/reactions@XstmIysIi_lWo6RzszLBt.md @@ -1 +1,7 @@ -# Reactions \ No newline at end of file +# 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/) \ No newline at end of file diff --git a/src/data/roadmaps/git-github/content/rebase@99FVJ3Zs8n6lr8L95mG6g.md b/src/data/roadmaps/git-github/content/rebase@99FVJ3Zs8n6lr8L95mG6g.md index ac1078166..707e0c8de 100644 --- a/src/data/roadmaps/git-github/content/rebase@99FVJ3Zs8n6lr8L95mG6g.md +++ b/src/data/roadmaps/git-github/content/rebase@99FVJ3Zs8n6lr8L95mG6g.md @@ -1 +1,7 @@ -# Rebase \ No newline at end of file +# 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) diff --git a/src/data/roadmaps/git-github/content/renaming-branch@_dPOVUbxApx0pfKPH8fgr.md b/src/data/roadmaps/git-github/content/renaming-branch@_dPOVUbxApx0pfKPH8fgr.md index 23f57625b..3836e15c0 100644 --- a/src/data/roadmaps/git-github/content/renaming-branch@_dPOVUbxApx0pfKPH8fgr.md +++ b/src/data/roadmaps/git-github/content/renaming-branch@_dPOVUbxApx0pfKPH8fgr.md @@ -1 +1,8 @@ -# Renaming Branch \ No newline at end of file +# 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/) diff --git a/src/data/roadmaps/git-github/content/squash@Z-srOhYFGVEKDexlJ6cjt.md b/src/data/roadmaps/git-github/content/squash@Z-srOhYFGVEKDexlJ6cjt.md index 65d6e5b7b..5580d8d87 100644 --- a/src/data/roadmaps/git-github/content/squash@Z-srOhYFGVEKDexlJ6cjt.md +++ b/src/data/roadmaps/git-github/content/squash@Z-srOhYFGVEKDexlJ6cjt.md @@ -1 +1,9 @@ -# Squash \ No newline at end of file +# 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) \ No newline at end of file