Repository ownership and names

[github-learning-lab]

This pull request is about repository ownership and naming conventions.

Challenge question

Does a repository exist at https://github.com/githubtraining/training-manual?

• True, there is a repository at the given URL
• False, no repository exists at the given URL

---

I'll respond when you check one of the boxes above.

[micsmith8]

reviewed

[micsmith8]

done

[github-learning-lab]

Answer 🔮

A repository does exist at githubtraining/training-manual, but it is private.

Why can't you see it then? Review the Files Changed tab and see if you can figure it out. Expand this text if you'd like an explanation.

Understanding repository visibility

There are three types of repository visibility: public, internal, and private.

Our repository, githubtraining/training-manual, isn't public. It could be internal, which means only members of the organizations that an account owns will see it. Or, it could be private, which means only teams and individuals that have been granted access to it can see it.

This is an example of why ownership structure is important. Otherwise, it can be difficult for members of your team to find and contribute to projects. Having too many disconnected organizations with restrictive permissions isolates each organization's work.

Here are some recommendations based on some ✨ admirable ✨ use of GitHub that we've seen:

• Use the internal visibility (currently in beta) if you're working on behalf of an enterprise account.
• Name your repositories meaningfully. Usually a simple project or application name is best.

---

⌨️ Activity: Review this pull request

1. Read the additions in the Files changed tab
2. Approve this pull request (if needed)
3. Merge this pull request
4. Delete the branch

---

I'll respond after you merge this pull request.

[micsmith8]

repopn

[github-learning-lab]

You can find your next steps in your next pull request.

[micsmith8]

done

[github-learning-lab]

Answer 🔮

This repository is the source code for https://services.github.com.

Did you guess it? Probably not, because it doesn't contain many of the necessary elements to make a repository discoverable.

Some suggestions to ensure your teammates can find your repository are:

• Use a descriptive repository name
• Give your repository a description
• Provide a URL for the deployment of the app, or documentation about this project

Discover more about how to make a repository discoverable by visiting the Files Changed tab. It's OK if you want to do this later, any resources we cover throughout the course will be available at the end.

⌨️ Activity: Discoverability

1. Review the additions about discoverability in the Files changed tab
2. Approve this pull request (if needed)
3. Merge this pull request
4. Delete the branch

---

I'll respond when you merge this pull request.

[micsmith8]

done