Forking a repository on GitHub is a common practice, especially when contributing to open- source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:
B). To propose changes to the base repository:
One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the "upstream" repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.
C). To create a new repository based on an existing one:
Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.

Markdown is an easy-to-read, easy-to-write language for formatting plain text. You can use Markdown syntax, along with some additional HTML tags, to format your writing on GitHub, in places like repository READMEs and comments on pull requests and issues.
Reference:
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and- formatting-on-github/quickstart-for-writing-on-github
https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/creating-a- saved-reply

Key Features of GitHub Flow
* Main Branch (main): This branch always contains deployable, production-ready code.
* Feature Branches: Developers create a new branch for each feature or bug fix. Once work on a feature is completed, a pull request (PR) is opened for review and merging into the main branch.
*-> Pull Requests: Once the feature branch is complete, a pull request is created to merge it into the main branch. The PR is reviewed and, once approved, is merged into main.
Reference:
https://www.geeksforgeeks.org/git/git-flow-vs-github-flow/

Filtering issues and pull requests
Issues and pull requests come with a set of default filters you can apply to organize your listings.
You can filter issues and pull requests to find:
All open issues and pull requests
[C] Issues and pull requests that you've created
[E] Issues and pull requests that are assigned to you
Issues and pull requests where you're @mentioned
Reference:
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/filtering-and- searching-issues-and-pull-requests

Setting up GitHub Copilot for yourself
Follow these steps to start using Copilot.
[A] 1. Get access to GitHub Copilot
There are a few ways that you can get access to GitHub Copilot:
* Use Copilot Free. Get a limited experience of Copilot with up to 2,000 code completion requests and 50 premium requests per month-no paid plan required. See About individual GitHub Copilot plans and benefits.
-> * Sign up for a paid plan.
* Etc.
[C] 2. 2. Install the Copilot extension for your IDE
If you want to use Copilot in your IDE, install the Copilot extension for your IDE.
Reference:
https://docs.github.com/en/copilot/how-tos/set-up/set-up-for-self