Add content to git/github roadmap (#6605)

src/data/roadmaps/git-github/content/--mixed@qis7Z5VRxMcOmbesQlegZ.md

@@ -2,4 +2,6 @@
 
 When using mixed mode, the HEAD pointer is moved to the specified commit. However, files in your working directory remain as they were before the reset. The staging area (index) is updated to match the specified commit.
 
+Visit the following resources to learn more:
+
 - [@official@--mixed documentation](https://git-scm.com/docs/git-reset#Documentation/git-reset.txt---hard)

src/data/roadmaps/git-github/content/basic-git-usage@PtU5Qwfzn3N1i3oRlCGoR.md

@@ -2,7 +2,7 @@
 
 Starting with a new project, you'll use `git init` to initialize a repository and then make changes using `git add`. Once ready, commit your work with `git commit`. If mistakes occur, `git reset` can help correct them. You'll also interact with remote repositories, whether private or public, by adding remotes (git remote add) and managing their connections through commands like `git fetch`, `git push`, and `git pull`.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@video@Git Tutorial for Beginners: Learn Git in 1 Hour](https://www.youtube.com/watch?v=8JJ101D3knE&t=1135s)
 - [@article@Git ignore](https://www.atlassian.com/git/tutorials/saving-changes/gitignore)

src/data/roadmaps/git-github/content/between-branches@O-zoAWkDvyn7B8_TmY257.md

@@ -2,5 +2,7 @@
 
 When comparing the differences between two branches, such as a feature branch and its upstream parent branch, use `git diff <branch1>..<branch2>`. This command displays the changes made on the feature branch relative to the parent branch. It's useful for reviewing the impact of new features or changes before merging them into your mainline.
 
+Visit the following resources to learn more:
+
 - [@article@How to compare branches in Git diff](https://scribehow.com/shared/How_to_Compare_Branches_in_GitHub__xsotezV-S1O-GL0PquqJwQ)
 - [@article@How can I see the differences between two branches?](https://stackoverflow.com/questions/9834689/how-can-i-see-the-differences-between-two-branches)

src/data/roadmaps/git-github/content/between-commits@Rwpeltygwzcf6hnuZNURE.md

@@ -2,5 +2,7 @@
 
 To compare two specific commits in your Git history, use git diff followed by the hashes of the commits. This will show you the changes made between those two points, including added, modified, and deleted lines.
 
+Visit the following resources to learn more:
+
 - [@article@Comparing changes with Git diff](https://refine.dev/blog/git-diff-command/)
 - [@video@Git Diff 2 Different Commits, Tags or Branches](https://www.youtube.com/watch?v=uq5VWPDCtFo)

src/data/roadmaps/git-github/content/collaborators--members@_ft-uvXt6s_xrcMT3fbSF.md

@@ -2,5 +2,7 @@
 
 In GitHub, collaborators and members refer to individuals who contribute to or have access to your repository. Collaborators are users who have been granted permission to contribute code, make changes, and push updates to your repository, whereas members are the owners of a repository, including organization owners who have full control over their team's repositories. Members can be either individual collaborators or part of an organization team, with varying levels of access and permissions based on their role within the team.
 
+Visit the following resources to learn more:
+
 - [@article@Inviting collaborators to a personal repository](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)
--[@official@REST API endpoints for collaborators](https://docs.github.com/en/rest/collaborators/collaborators?apiVersion=2022-11-28)
+- [@official@REST API endpoints for collaborators](https://docs.github.com/en/rest/collaborators/collaborators?apiVersion=2022-11-28)

src/data/roadmaps/git-github/content/github-actions@AmetdCURXXob5TUsikAab.md

@@ -4,5 +4,7 @@ GitHub Actions is a very useful tool for automation, allowing developers to auto
 
 One of the best ways to learn about GitHub Actions is through the course offered by Microsoft Learn. This course is well-structured and provides practical examples that are concise and easy to understand.
 
+Visit the following resources to learn more:
+
 - [@course@Microsoft Learn: Introduction to GitHub Actions](https://learn.microsoft.com/en-us/collections/n5p4a5z7keznp5)
 - [@course@YouTube: GitHub Actions Playlist](https://www.youtube.com/watch?v=-hVG9z0fCac&list=PLArH6NjfKsUhvGHrpag7SuPumMzQRhUKY&pp=iAQB)

src/data/roadmaps/git-github/content/github-api@NV2HAXLEN7tskfgyFrbaf.md

@@ -2,7 +2,7 @@
 
 The GitHub API is a powerful tool that allows developers to interact with the GitHub platform programmatically. It provides access to various GitHub features, such as user data, repository information, and commit history, through both REST and GraphQL interfaces. The API supports authentication, implements rate limiting, and offers webhooks for real-time notifications, enabling developers to automate tasks, create custom integrations, and build applications that leverage GitHub's functionality.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@official API Docs](https://docs.github.com/en/rest?apiVersion=2022-11-28)
 - [@article@Getting started](https://docs.github.com/en/rest/using-the-rest-api/getting-started-with-the-rest-api?apiVersion=2022-11-28)

src/data/roadmaps/git-github/content/github-cli@h9cf_dh_pwjialOXOlNW-.md

@@ -2,7 +2,7 @@
 
 GitHub CLI is a command-line interface tool that brings GitHub functionality to your terminal. It allows developers to interact with GitHub directly from the command line, enabling them to manage repositories, create issues, pull requests, and perform various GitHub operations without leaving their terminal environment. This powerful tool streamlines workflows, enhances productivity, and provides a seamless integration between local development and GitHub's collaborative features, making it easier for developers to incorporate GitHub into their daily coding routines.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@official GitHub CLI Docs](https://cli.github.com/)
 - [@video@What is the GitHub CLI?](https://www.youtube.com/watch?v=uy_PEGgUF4U)

src/data/roadmaps/git-github/content/github-discussions@snWQHCQECZyUXHdn6ppIk.md

@@ -2,7 +2,7 @@
 
 GitHub Discussions is a collaborative communication feature within GitHub repositories that provides a dedicated space for community conversations, questions, and knowledge sharing. It allows team members, contributors, and users to engage in threaded discussions, share ideas, ask for help, and make announcements outside of specific code changes or issues. This feature enhances project collaboration by centralizing important conversations, reducing noise in the issue tracker, and fostering a sense of community around open-source projects or team initiatives.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@video@What is GitHub Discussions?](https://www.youtube.com/watch?v=bErGYN3Ljz8)
 - [@official@official GitHub Discussions Docs](https://docs.github.com/en/discussions)

src/data/roadmaps/git-github/content/github-education@pFyMiyNQ16-kP7jKaKKEU.md

@@ -2,7 +2,7 @@
 
 GitHub Education is a program that provides free and discounted access to GitHub's developer tools, services, and resources for students, teachers, and researchers. This program aims to support education and research in software development, by making it easier for students and educators to learn, collaborate, and build projects on GitHub. By using GitHub Education, students can gain hands-on experience with real-world coding challenges, while educators can create a more engaging and interactive learning environment.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@official GitHub Education Docs](https://education.github.com/)
 - [@video@GitHub GitHub Education: free programs, technology, and opportunities available for Students](https://www.youtube.com/watch?v=HIVFdN9VGgw)

src/data/roadmaps/git-github/content/github-interface@qZFtRABvlBbVvsy6T00J2.md

@@ -2,7 +2,7 @@
 
 The GitHub interface is a web-based platform that provides a user-friendly environment for managing and collaborating on software projects. It offers a comprehensive set of tools and features accessible through an intuitive layout, including repository management, code browsing, issue tracking, pull requests, and project boards. The interface is designed to streamline workflows, facilitate team communication, and enhance productivity for developers of all skill levels. With its clean and organized structure, users can easily navigate between different sections of their projects, review code changes, manage tasks, and interact with team members, making it an essential tool for modern software development and version control.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@GitHub Desktop App](https://github.com/apps/desktop)
 - [@article@Getting Started with GitHub](https://digital.gov/resources/an-introduction-github/)

src/data/roadmaps/git-github/content/github-organizations@RMrxQLhrINO5g4Mhxh5qS.md

@@ -2,7 +2,7 @@
 
 GitHub Organizations are shared accounts that provide centralized management and collaboration for multiple projects and teams. They offer enhanced administrative controls, allowing owners to create teams with specific access permissions, manage member roles, and oversee repositories at scale. Organizations facilitate better project coordination, resource sharing, and team communication, making them ideal for businesses, open-source projects, and large-scale collaborations. With features like team discussions, project boards, and audit logs, GitHub Organizations streamline workflow management and foster a more structured and secure development environment.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@About Organizations](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations)
 - [@video@Set up a GitHub Organization](https://www.youtube.com/watch?v=XowSSIhJFuk)

src/data/roadmaps/git-github/content/github-projects@DzFJDdqnSy5GeGHWOpcVo.md

@@ -2,7 +2,7 @@
 
 GitHub Projects is a flexible project management tool integrated directly into GitHub repositories. It allows teams to create customizable project boards, track issues and pull requests, and manage workflows using Kanban-style columns or table views. With features like automated workflows, custom fields, and various visualization options, GitHub Projects helps teams organize, prioritize, and track work across multiple repositories. This tool enhances collaboration, increases transparency, and streamlines project management processes, making it easier for developers and stakeholders to stay aligned on project goals and progress.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@About Projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)
 - [@video@How to use Projects Roadmap](https://www.youtube.com/watch?v=D80u__nYYWw)

src/data/roadmaps/git-github/content/github-releases@YmnTrjJtqHPXbEVrP8vd7.md

@@ -2,7 +2,7 @@
 
 GitHub Releases is a feature that allows developers to package and distribute software versions to users. It provides a way to create tagged points in a repository's history, attach binary files (such as compiled executables or packaged code), and include release notes. This feature makes it easy to track and manage different versions of a project, share pre-compiled binaries with users who may not want to build from source, and communicate changes and updates to the community. GitHub Releases integrates seamlessly with Git tags and can be automated as part of a continuous integration and deployment pipeline.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@About Releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases)
 - [@article@REST API endpoints for releases](https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28)

src/data/roadmaps/git-github/content/github-wikis@Ddkss13_qDJTquDHbVTVs.md

@@ -2,7 +2,7 @@
 
 GitHub Wikis are collaborative documentation spaces integrated directly into GitHub repositories. They provide a platform for teams to create, edit, and organize project-related information, such as documentation, guidelines, and FAQs. Wikis support Markdown formatting, making it easy to structure content and include images or links. With version control and the ability to clone wiki repositories, teams can collaboratively maintain up-to-date documentation alongside their code, enhancing project understanding and facilitating knowledge sharing among contributors and users.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@About Wikis](https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis)
 - [@article@Documenting your project with Wikis](https://docs.github.com/en/communities/documenting-your-project-with-wikis)

src/data/roadmaps/git-github/content/gitignore@oz2oRAhaEQb0Fm3aRJQG8.md

@@ -2,7 +2,7 @@
 
 Ignored files are tracked in a special file named `.gitignore` that is checked in at the root of your repository. There is no explicit git ignore command: instead the `.gitignore` file must be edited and committed by hand when you have new files that you wish to ignore. `.gitignore` files contain patterns that are matched against file names in your repository to determine whether or not they should be ignored.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@official@gitignore Documentation](https://git-scm.com/docs/gitignore/en)
 - [@article@.gitignore file - ignoring files in Git | Atlassian Git Tutorial](https://www.atlassian.com/git/tutorials/saving-changes/gitignore)

src/data/roadmaps/git-github/content/handling-conflicts@9Dt4Gyiiq5jteWSKxsRMK.md

@@ -1 +1,9 @@
 # Handling Conflicts
+
+When multiple developers work on the same project simultaneously, conflicts can arise during the merging process. This occurs when changes made by different individuals overlap or contradict each other in a specific code file. In such situations, Git's conflict resolution mechanism comes into play, allowing users to manually resolve these issues and merge the conflicting changes.
+
+Visit the following resources to learn more:
+
+- [@article@Resolving a merge conflict using the command line](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
+- [@article@Resolve merge conflicts in Visual Studio](https://learn.microsoft.com/en-us/visualstudio/version-control/git-resolve-conflicts?view=vs-2022)
+- [@video@Resolve Git MERGE CONFLICTS: The Definitive Guide](https://www.youtube.com/watch?v=Sqsz1-o7nXk)

src/data/roadmaps/git-github/content/head@V8nLIvddyOKTzEjOJX5GW.md

@@ -1 +1,8 @@
 # HEAD
+
+The `HEAD` file is at the core of how Git knows the SHA-1 of the last commit when running commands like `git branch <branch>`. It serves as a symbolic reference, pointing to the current branch. However, in rare cases, HEAD can contain the actual SHA-1 value of a Git object, such as when checking out a tag, commit, or remote branch, which puts your repository in a "detached HEAD" state.
+
+Visit the following resources to learn more:
+
+- [@official@Git Internals - Git References - The HEAD](https://git-scm.com/book/en/v2/Git-Internals-Git-References#:~:text=want%20to%20create.-,The%20HEAD,-The%20question%20now)
+- [@video@Learn Git Essentials: Head & Detached Head](https://www.youtube.com/watch?v=HvDjbAa9ZsY)

src/data/roadmaps/git-github/content/history@zen3RRdK9_nPAYgicRoHk.md

@@ -1 +1,7 @@
 # History
+
+The history of a Git repository is a record of all commits made over time, including changes to files, commit messages, and metadata. This history is stored as a series of snapshots, with each commit representing a new version of the codebase.
+
+Visit the following resources to learn more:
+
+- [@official@Git Basics - Viewing the Commit History](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History)

src/data/roadmaps/git-github/content/installation-and-setup@vHfpoVbOW0DHNtiy0VN4X.md

@@ -1 +1,11 @@
 # Installation and Setup
+
+The GitHub CLI can be installed on Windows, macOS, and Linux operating systems. Installation options include downloading binaries directly from the release page or using package managers (such as homebrew, pip, etc).
+
+Once installed, setting up the GitHub CLI typically involves authenticating with your GitHub account by running `gh auth login` in your terminal. This step is essential for linking your GitHub credentials to the CLI, allowing you to interact with your repositories and perform various actions.
+
+Visit the following resources to learn more:
+
+- [@official@GitHub CLI - Installation](https://github.com/cli/cli?tab=readme-ov-file#installation)
+- [@official@GitHub CLI - Release](https://github.com/cli/cli/releases/)
+- [@official@GitHub CLI quickstart](https://docs.github.com/en/github-cli/github-cli/quickstart)

src/data/roadmaps/git-github/content/installing-git-locally@v7hCNbgPByi3YiLSs46BK.md

@@ -1 +1,14 @@
 # Installing Git Locally
+
+To use Git on your local machine, you need to install it first. The installation process varies depending on your operating system:
+
+- On Windows: Download the binary from the official Git or GitHub release page and follow the installation instructions.
+- On macOS (using Homebrew): Run `brew install git` in your terminal.
+- On Linux: Run `sudo apt-get install git` or `sudo yum install git` depending on your distribution.
+
+Once installed, you can verify the Git version by running `git --version` in your terminal. This will display the currently installed Git version.
+
+Visit the following resources to learn more:
+
+- [@official@Git - Downloads](https://git-scm.com/downloads)
+- [@article@Install Git](https://github.com/git-guides/install-git)

src/data/roadmaps/git-github/content/issue-management@kGnZifvXbHBf5zXIsfAQw.md

@@ -1 +1,14 @@
 # Issue Management
+
+The GitHub CLI provides a range of features for managing issues within your repository. Here are some key actions you can perform:
+
+- Listing issues: Run `gh issue list` to view a list of all open and closed issues.
+- Creating issues: Use `gh issue create --title "Issue Title" --body "Issue body"` to create a new issue with the specified title and body.
+- Assigning issues: Run `gh issue assign <issue-number> <username>` to assign an issue to a specific user.
+- Labelling issues: Use `gh issue label <issue-number> <label-name>` to add a label to an existing issue.
+- Closing issues: Run `gh issue close <issue-number>` to mark an issue as closed.
+
+Visit the following resources to learn more:
+
+- [@official@gh issue](https://cli.github.com/manual/gh_issue)
+- [@video@Manage GitHub Issues From The Command Line Using GitHub CLI](https://www.youtube.com/watch?v=nuCQiP41jU0)

src/data/roadmaps/git-github/content/issues@crdllx5cH_seIpgVPvHg_.md

@@ -1 +1,18 @@
 # Issues
+
+On GitHub, an issue is a way to track and report bugs, feature requests, or other problems with a repository. Here are some key aspects of issues:
+
+- Creating issues: Users can create new issues by submitting a form on the repository's Issues page.
+- Issue titles and descriptions: Each issue has a title and body (description), which provide context for the problem or request.
+- Assignees: Issues can be assigned to specific users, who are then responsible for addressing the issue.
+- Labels: Labels are used to categorize issues by topic, priority, or other criteria. This helps filter and organize issues within a repository.
+- States: Issues have states that reflect their status, such as "Open", "Closed", or "Pending".
+- Comments: Users can comment on existing issues to discuss or provide additional context.
+- Labels and milestones: Issues can be associated with labels (topics) and milestones (deadlines), which help filter and prioritize them.
+
+Issues are a core feature of GitHub repositories, enabling teams to collaborate effectively on resolving problems and implementing new features.
+
+Visit the following resources to learn more:
+
+- [@official@About Issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues)
+- [@video@What is GitHub Issues?](https://www.youtube.com/watch?v=6HWw7rhwvtY)

src/data/roadmaps/git-github/content/kanban-boards@RFJgfuxoVxt22QlwLI5mW.md

@@ -1 +1,10 @@
 # Kanban Boards
+
+On GitHub, Kanban boards provide a visual representation of issues as they move through the development process.
+
+A Kanban board typically has columns representing different stages or states, such as "To-Do", "In-Progress", and "Done". Each issue is represented by a card on the board, which can be moved between columns as its state changes. Users can drag and drop issue cards to move them from one column to another, reflecting progress or completion.
+
+Visit the following resources to learn more:
+
+- [@official@Projects - Boards - Changing the layout of a view](https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view)
+- [@video@GitHub Project Management - Create GitHub Project Board & Automations](https://www.youtube.com/watch?v=oPQgFxHcjAw)

src/data/roadmaps/git-github/content/labelling-issues--prs@y4DkB5NvTh41IeT0G2gr-.md

@@ -1 +1,14 @@
 # Labelling Issues / PRs
+
+On GitHub, labels are a way to categorize issues and pull requests (PRs) by topic, priority, or other criteria. Some common labels used are:
+
+- `Bug`
+- `Duplicate`
+- `Enhancement`
+- `Feature request`
+- `High priority`
+- `Needs feedback`
+
+Visit the following resources to learn more:
+
+- [@official@Managing labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels)

src/data/roadmaps/git-github/content/learn-the-basics@HlUUGj3dOZ68t4gIjerXh.md

@@ -2,7 +2,7 @@
 
 A Version Control System (VCS) is a tool that helps developers manage changes to their code over time. It allows multiple versions of a project to exist simultaneously, making it easier to collaborate with others and maintain a record of all modifications.
 
-Learn more from the following resources:
+Visit the following resources to learn more:
 
 - [@article@What is version control?](https://www.atlassian.com/git/tutorials/what-is-version-control)
 - [@article@What is Git? - The Complete Guide to Git](https://www.datacamp.com/blog/all-about-git)

src/data/roadmaps/git-github/content/linear-vs-non-linear@lXC07j6dOa3rQixY1P-Ob.md

@@ -1 +1,11 @@
 # Linear vs Non-Linear
+
+In Git, linear and non-linear history refer to different ways of managing commit history.
+
+- Linear history: A repository with a linear history has commits that are applied in a single, sequential order.
+- Non-linear history: A repository with a non-linear history allows multiple branches or lines of development, which can be merged back into the main branch at different points.
+
+Visit the following resources to learn more:
+
+- [@article@Linear vs Non-Linear History](https://idiv-biodiversity.github.io/git-knowledge-base/linear-vs-nonlinear.html)
+- [@article@Linear git history - Part I](https://jun-sheng.medium.com/linear-git-history-part-i-b97184dde252#:~:text=The%20benefit%20of%20having%20a%20linear%20git%20history&text=It%20is%20easier%20to%20understand,bisect%20to%20track%20a%20bug.)

src/data/roadmaps/git-github/content/local-vs-global-config@tVvxC5JQgUb_B8kOqYpD8.md

@@ -1 +1,11 @@
 # Local vs Global Config
+
+To manage local and global configuration settings, you can use the git config command with the --local and --global options.
+
+- Local configuration: Run `git config --local [key] [value]` to set a local configuration setting for the current repository.
+- Global configuration: Use `git config --global [key] [value]` to set a global configuration setting that applies to all repositories on your system.
+
+Visit the following resources to learn more:
+
+- [@official@Customizing Git - Git Configuration](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration)
+- [@article@A step-by-step guide to setting up global Git config properties](https://medium.com/geekculture/a-step-by-step-guide-to-setting-up-git-config-global-properties-db6dbce30fa8)

src/data/roadmaps/git-github/content/managing-remotes@sBQOInoFBU9XfkPZ-JlyT.md

@@ -1 +1,14 @@
 # Managing Remotes
+
+In Git, a remote repository refers to a copy of a project's source code stored on a server or other machine.
+
+- Adding remotes: Use `git remote add [name] [url]` to add a new remote repository. This allows you to track changes and push/pull updates from the remote.
+- Listing remotes: Run `git remote -v` to list all configured remotes with their URLs.
+- Renaming remotes: Update the name of an existing remote using `git remote rename [old-name] [new-name]`.
+- Deleting remotes: Remove a remote repository with `git remote remove [name]`.
+
+Managing remotes is essential for collaborating on projects or tracking changes from upstream sources.
+
+Visit the following resources to learn more:
+
+- [@official@Managing remote repositories](https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories)

src/data/roadmaps/git-github/content/managing-tags@NeU38WPbEphJuJ_AMkH82.md

@@ -1 +1,14 @@
 # Managing Tags
+
+In Git, a tag is a named reference to a specific commit in the project's history.
+
+- Creating tags: Use `git tag [name] [commit-hash]` to create a new tag. You can also use `git tag -a [name] -m "[message]" [commit-hash]` for annotated tags.
+- Listing tags: Run `git tag` to display all existing tags.
+- Deleting tags: Remove an existing tag with `git tag -d [tag-name]`.
+
+Tags can be used for marking releases, milestones, or other significant events in a project's history.
+
+Visit the following resources to learn more:
+
+- [@official@Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)
+- [@article@Git — Use Tags for Versioning and Release Management](https://medium.com/@KeyurRamoliya/git-use-tags-for-versioning-and-release-management-09aca9631eee)

src/data/roadmaps/git-github/content/markdown@1Ulxl4VUvRSfyCPpi-iv8.md

@@ -1 +1,14 @@
 # Markdown
+
+Markdown is a simple way to add formatting to text without using HTML tags or other complex syntax. It's easy to read and write, making it suitable for documentation, README files, and more. Some basic GitHub Markdown features include:
+
+- Basic syntax: Use headers (`# Heading`), bold/italic text (**bold**, *italic*), and lists (- item) to format text.
+- Links: Create links with `[text](url)` or `[text][ref]`.
+- Images: Embed images with `[![alt-text](image-url)]`.
+
+By using Markdown, you can easily format text within your GitHub repository, making it easier to read and understand for yourself and others.
+
+Visit the following resources to learn more:
+
+- [@official@Basic writing and formatting syntax](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)
+- [@article@Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)

src/data/roadmaps/git-github/content/marketplace-actions@SsogoCgJIbeTD6tk8UhTe.md

@@ -1 +1,13 @@
 # Marketplace Actions
+
+The GitHub Marketplace offers a wide range of pre-built actions that can be used to automate tasks and workflows within your repository.
+
+- Automate tasks: Use marketplace actions to automate tasks such as testing, deployment, or security.
+- Customize workflows: Create custom workflows using marketplace actions to tailor the build process to specific needs.
+- Streamline development: By automating repetitive tasks, developers can focus on code quality and collaboration.
+
+These actions are created by the GitHub community and can be easily added to your workflow to enhance productivity and efficiency.
+
+Visit the following resources to learn more:
+
+- [@official@GitHub MarketPlace - Actions](https://github.com/marketplace?type=actions)

src/data/roadmaps/git-github/content/mentions@oWMaOWU06juoIuzXNe-wt.md

@@ -1 +1,3 @@
 # Mentions
+
+Mentions on GitHub allow you to notify specific users or teams about comments, issues, pull requests, or other activities. This feature improves collaboration by encouraging participation and discussion among team members, increasing visibility of important topics, and streamlining communication within your repository. To use mentions, simply type `@username` or `@teamname` in a comment, and GitHub will auto-complete the mention as you type, automatically linking their username to the comment and notifying them about the discussion.

src/data/roadmaps/git-github/content/merge-strategies@0rHDUbAdXqH9zQW2VfJ8v.md

@@ -1 +1,9 @@
 # Merge Strategies
+
+When combining changes from one branch into another, Git provides various merge strategies to choose from. These methods allow for flexibility and customization in integrating code updates into your main branch. The available options include:
+
+- Fast Forward (FF)
+- Non-Fast Forward
+- Rebase
+- Squash
+- Cherry Picking

src/data/roadmaps/git-github/content/merging-basics@sNuy6NMjLOEkJlqdEjFPq.md

@@ -1 +1,8 @@
 # Merging Basics
+
+A merge in Git is the process of combining changes from one branch into another. When you want to integrate updates from one branch (the source) into another branch (the target), you need to perform a merge. This involves resolving conflicts between the two branches, if any exist. The goal of merging is to create a new commit that represents the combined changes from both branches, resulting in a single, cohesive history for your project.
+
+Visit the following resources to learn more:
+
+- [@official@Git Branching - Basic Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging#:~:text=into%20master%20later.-,Basic%20Merging,-Suppose%20you%E2%80%99ve%20decided)
+- [@article@Git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge)