You have one more decision to make before you migrate your code! Right now, your repository is set to public.
You can change the visibility of a repository to Private or Public at any time in your repository's Settings tab, but there are some things you should know.
Private Repositories
If your repository is private, the only people who can see your code are you and the collaborators :book: you've invited.
There is a small charge associated with Private repositories, but if your project has sensitive information, it's worth it.
Public Repositories
In public repositories, anybody can see your code. Millions of open source repositories on GitHub are public, too!
Licenses, code of conduct, and other files are important when you create a public repository. There are many benefits to this, but it's also a large responsibility. Keep in mind that once a repository is public and open source, there are certain implications about keeping it public, depending on the license chosen.
It's important to note that public does not equal open source! The license associated with code determines whether or not it is open source.
When you are finished, close this issue. I will open a new issue with the next steps. :tada:
Watch below for my response
:robot: I'm waiting for you to close this issue before moving on.
github-learning-lab[bot]
commented
6 years ago
Step 3: Private or Public?
You have one more decision to make before you migrate your code! Right now, your repository is set to public.
You can change the visibility of a repository to Private or Public at any time in your repository's Settings tab, but there are some things you should know.
Private Repositories
If your repository is private, the only people who can see your code are you and the collaborators :book: you've invited.
There is a small charge associated with Private repositories, but if your project has sensitive information, it's worth it.
Public Repositories
In public repositories, anybody can see your code. Millions of open source repositories on GitHub are public, too!
Licenses, code of conduct, and other files are important when you create a public repository. There are many benefits to this, but it's also a large responsibility. Keep in mind that once a repository is public and open source, there are certain implications about keeping it public, depending on the license chosen.
It's important to note that public does not equal open source! The license associated with code determines whether or not it is open source.
Watch below for my response