Exploring a Repository

Kent C. Dodds
InstructorKent C. Dodds
Share this video with your friends

Social Share Links

Send Tweet
Published 8 years ago
Updated 5 years ago

The basic unit of GitHub is a repository. This is where your code is stored and GitHub allows you to interact with others and with the code in great ways. In this lesson we talk about Watching, Starting, and Forking a repository. We also cover GitHub issues and pull requests and various other stats about a GitHub repository.

[00:00] the basic unit of GitHub is a repository. Let's explore this repository for a minute. There are a few things that you can do up here at the top.

[00:07] First, you can watch the repository. This has to do with notifications that you'll be receiving. You can configure these notifications to notify you just in the web client here with the bell, or also in email.

[00:19] If you select watching on a repository, you'll receive notifications for every conversation that's had in pull request and issues. If you set to not watching, which is the default, you'll only be notified when you are participating or at mentioned. If you say ignored, then, you'll never be notified even if you're mentioned or if you're participating in a conversation.

[00:38] Next is the star. If we star this repository, then, we can go to our GitHub.com/stars page. This will show that repository starred in our stars page.

[00:50] This is a way to bookmark a repository, and also, show appreciation to the repository author for the work that they've done. This also impacts GitHub trends. It's another way that GitHub uses to recognize the popularity or the trendingness of a repository,

[01:06] We can also fork a repository. This basically makes a copy of the repository that is associated with your user. If I click can see dots here, it's gong to make a copy of this repository that is forked from egghead IO GitHub Stack Overflow copy paste.

[01:22] I have the exact same code in my repository. I can pull it down. I can push changes to it, do whatever I want with it, because it is my very own repository. We'll look at this a little bit more later.

[01:34] Let's go back to the original repository. For the code area, we see all the code listed here. We can browse it. If there is a read me file in the directory that we're looking, GitHub will automatically render that file at the bottom of the code area. In this case, it's markdown. That's the .md extension. It will also render a couple other formats as well.

[01:55] I recommend that you learn about Markdown. If we look at this readme.md file and look at the raw, we'll see that it's simply code that can be rendered in our GitHub repository. If you want to learn more about how GitHub parses this markdown, you can simply Google GitHub flavored markdown. it will probably be the first result. You can learn more about that here.

[02:17] The next area is the issues. This is where we would collaborate with the project maintainer on features that we want to have implemented or bugs that we've found in the project.

[02:27] Depending on the project, this is also a good place to ask questions. However, many projects have a chat or another mechanism for asking questions like Stack Overflow. You'll want to check the contributing guidelines first. We'll look at that a little bit later.

[02:41] You can also be 99 percent sure that any project maintainer would be fine for you to file an issue that thanks them for their hard work on the project. Feel free to do that here.

[02:49] The next thing as pull requests. A pull request is when you have changes in your own copy of the repository that you would like to have merged with the main repository. You would file a pull request here and iterate on your solution with the project maintainer before they actually merge your changes into the main repository.

[03:06] Next is the wiki. Some projects have a wiki, some don't. But the wiki is a good place for some documentation if you don't want to put that in the read me or some contributing guidelines and other things of that nature.

[03:17] Then, you have the pulse. This will give you an overview of how active the project is. Then, you have graphs. This will give you interesting information about who's contributed to the project.

[03:27] If you have access to the repository, you also get to see some of the traffic that has been coming to the repository. You also get a sense of the commits, when code is being contributed.

[03:41] Network is actually really useful. If a project appears to be inactive, you can look at the network and see other forks of the project to see if anyone else is maintaining the project.

[03:52] Finally, you have the members of people who can contribute to the project. T

[03:57] Then finally, if you own the repository, you also have settings. That will give additional settings for the project as a project maintainer.

[04:04] That's an exploration of the GitHub repository...

~ 2 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today