Open source software (OSS) can be freely used, modified, and shared because its source code is publicly available under specific licenses. These open source licenses grant users the freedom to access, study, change, and distribute the software to anyone, fostering transparency, collaboration, and innovation within a global community.
Reference:
https://en.wikipedia.org/wiki/Free_and_open-source_software

Repository visibility
There are three visibility types for repositories: public, internal, and private.
Public repositories are visible to the world and are primarily used for open source content.
Internal repositories are read-accessible to all full members of your enterprise account (not to outside collaborators).
Private repositories are only visible to individuals or teams who have been given explicit access, including through enterprise or organization base permissions.
Reference:
https://resources.github.com/learn/pathways/administration-governance/essentials/manage-your- repository-visibility-rules-and-settings/

Pinning an issue to your repository
You can pin up to three important issues above the issues list in your repository.
Who can use this feature?
People with write access to a repository can pin issue in the repository.
1. On GitHub, navigate to the main page of the repository.
2. Under your repository name, click Issues.

3. In the list of issues, click the issue you'd like to pin.
4. In the right sidebar, click Pin issue.
Reference:
https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/pinning- an-issue-to-your-repository

A remote in Git is a common repository that all team members use to exchange their changes. In most cases, such a remote repository is stored on a code hosting service like GitHub or on an internal server.
About remote repositories
GitHub's collaborative approach to development depends on publishing commits from your local repository to GitHub for other people to view, fetch, and update.
Note:
A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
You can only push to two types of URL addresses:
An HTTPS URL like https://github.com/user/repo.git
An SSH URL, like [email protected]:user/repo.git
Git associates a remote URL with a name, and your default remote is usually called origin.
Reference:
https://docs.github.com/en/get-started/git-basics/about-remote-repositories

Creating a new repository
You can create a new repository on your personal account or any organization where you have sufficient permissions.
If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to GitHub, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later.
You can create a README, which is a document describing your project. For more information, see About the repository README file.
You can create a .gitignore file, which is a set of ignore rules. For more information, see Ignoring files.
You can choose to add a software license for your project. For more information, see Licensing a repository.
Reference:
https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new- repository