Skip to main content
설명서에 자주 업데이트를 게시하며 이 페이지의 번역이 계속 진행 중일 수 있습니다. 최신 정보는 영어 설명서를 참조하세요.

리포지토리 간 연결 이해

네트워크 그래프 및 포크 목록을 사용하여 포크 네트워크를 이해합니다.

이 리포지토리 인사이트 그래프는 GitHub Free 및 조직에 대한 GitHub Free가 있는 퍼블릭 리포지토리와 GitHub Pro, GitHub Team, GitHub Enterprise Cloud, GitHub Enterprise Server가 있는 퍼블릭 및 프라이빗 리포지토리에서 사용할 수 있습니다. 자세한 내용은 “리포지토리 그래프 정보” 및 “GitHub 제품”을 참조하세요.

Viewing a repository's network

The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.

Repository network graph

Tip: To see older branches, click and drag within the graph.

Accessing the network graph

  1. On GitHub.com, navigate to the main page of the repository.
  2. Under your repository name, click Insights. Insights tab in the main repository navigation bar
  3. In the left sidebar, click Network. Network tab

Listing the forks of a repository

The Members graph displays all the forks of a repository.

Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's GitHub Enterprise Cloud profile page or click on the fork name to be redirected to the specific fork of the repository.

Repository members graph

Accessing the Members graph

  1. On GitHub.com, navigate to the main page of the repository.
  2. Under your repository name, click Insights. Insights tab in the main repository navigation bar
  3. In the left sidebar, click Forks. Forks tab

Viewing the dependencies of a repository

You can use the dependency graph to explore the code your repository depends on.

Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.

The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "About the dependency graph" and "Exploring the dependencies of a repository."

You can also set up your repository so that GitHub alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "About Dependabot alerts."