Hello git history spelunker!

Are you looking for something? Here is all of the GitHub Docs history in one single commit. Enjoy! 🎉

content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md

@@ -0,0 +1,32 @@
+---
+title: About repository graphs
+intro: Repository graphs help you view and analyze data for your repository.
+redirect_from:
+  - /articles/using-graphs/
+  - /articles/about-repository-graphs
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+A repository's graphs give you information on {% if currentVersion == "free-pro-team@latest" %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+Some repository graphs are available only in public repositories with {{ site.data.variables.product.prodname_free_user }}:
+- Pulse
+- Contributors
+- Traffic
+- Commits
+- Code frequency
+- Network
+
+All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {{ site.data.variables.product.prodname_pro }}, {{ site.data.variables.product.prodname_team }}, and {{ site.data.variables.product.prodname_ghe_cloud }}. {{ site.data.reusables.gated-features.more-info }}
+
+{% endif %}
+
+### Further reading
+
+- "[Accessing basic repository data](/articles/accessing-basic-repository-data)"
+- "[Analyzing changes to a repository's content](/articles/analyzing-changes-to-a-repository-s-content)"
+- "[Understanding connections between repositories](/articles/understanding-connections-between-repositories)"

content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md

@@ -0,0 +1,85 @@
+---
+title: About the dependency graph
+intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+### Dependency graph availability
+
+The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+
+{{ site.data.reusables.repositories.enable-security-alerts }}
+
+### About the dependency graph
+
+The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+
+- Dependencies, the ecosystems and packages it depends on
+- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {{ site.data.variables.product.prodname_ghe_server }} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+
+When you push a commit to {{ site.data.variables.product.product_name }} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+
+### Dependencies included
+
+The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+
+- Direct dependencies, that are explicitly defined in a manifest or lock file
+- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+
+The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Dependents included
+
+For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+
+### Using the dependency graph
+
+You can use the dependency graph to:
+
+- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
+- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
+- View and update vulnerable dependencies for your repository. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+
+### Enabling the dependency graph
+
+{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {{ site.data.variables.product.product_name }} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
+
+
+{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {{ site.data.variables.product.prodname_dependabot_short }} alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {{ site.data.variables.product.prodname_ghe_server }}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+
+{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {{ site.data.variables.product.prodname_ghe_server }}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+
+{% endif %}
+
+When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+
+### Supported package ecosystems
+
+The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+
+| Package manager | Languages | Recommended formats | All supported formats |
+| --- | --- | --- | ---|
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |{% endif %}
+| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+| Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
+| npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
+| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* |
+| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
+| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+
+{% note %}
+
+**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+
+{% endnote %}
+
+### Further reading
+
+- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
+- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
+- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}

content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md

@@ -0,0 +1,11 @@
+---
+title: Accessing basic repository data
+intro: 'You can view basic information about a repository, such as the repository''s activity{% if currentVersion == "free-pro-team@latest" %}, traffic,{% endif %} and contribution activity.'
+mapTopic: true
+redirect_from:
+  - /articles/accessing-basic-repository-data
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+

content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md

@@ -0,0 +1,13 @@
+---
+title: Analyzing changes to a repository's content
+intro: 'You can see the changes to the content of a repository by analyzing the repository''s commits, commit frequency, and content additions and deletions.'
+redirect_from:
+  - /articles/viewing-commit-frequency-in-a-repository/
+  - /articles/analyzing-changes-to-a-repository-s-content
+  - /articles/analyzing-changes-to-a-repositorys-content
+mapTopic: true
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+

content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md

@@ -0,0 +1,113 @@
+---
+title: Exploring the dependencies of a repository
+intro: 'Using the dependency graph, you can see the packages your project depends on{% if currentVersion == "free-pro-team@latest" %} and the repositories that depend on it{% endif %}. In addition, you can see any vulnerabilities detected in its dependencies.'
+redirect_from:
+  - /articles/listing-the-packages-that-a-repository-depends-on
+  - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on
+  - /articles/listing-the-projects-that-depend-on-a-repository
+  - /github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository
+  - /github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+### Viewing the dependency graph
+
+{{ site.data.reusables.repositories.enable-security-alerts }}
+
+The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+{{ site.data.reusables.repositories.click-dependency-graph }}{% if currentVersion == "free-pro-team@latest" %}
+4. Optionally, under "Dependency graph", click **Dependents**.
+![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+
+#### Dependencies view
+
+{% if currentVersion == "free-pro-team@latest" %}
+Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies on public repositories hosted on {{ site.data.variables.product.product_name }}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text.
+
+If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {{ site.data.variables.product.prodname_dependabot_alerts }}.
+
+![Dependencies graph](/assets/images/help/graphs/dependencies_graph.png)
+
+{% endif %}
+
+{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}
+Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {{ site.data.variables.product.prodname_dependabot_short }} alerts.
+
+{% note %}
+
+**Note:** {{ site.data.variables.product.prodname_ghe_server }} does not populate the **Dependents** view.
+
+{% endnote %}
+
+![Dependencies graph](/assets/images/help/graphs/dependencies_graph_server.png)
+
+{% note %}
+
+**Note:** {{ site.data.variables.product.prodname_ghe_server }} does not populate the **Dependents** view.
+
+{% endnote %}
+
+{% endif %}
+
+{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %}
+Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
+
+{% note %}
+
+**Note:** {{ site.data.variables.product.prodname_ghe_server }} does not populate the **Dependents** view.
+
+{% endnote %}
+
+![Dependencies graph](/assets/images/help/graphs/dependencies_graph_server.png)
+
+{% note %}
+
+**Note:** {{ site.data.variables.product.prodname_ghe_server }} does not populate the **Dependents** view.
+
+{% endnote %}
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Dependents view
+
+For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
+
+![Dependents graph](/assets/images/help/graphs/dependents_graph.png)
+
+### Enabling and disabling the dependency graph for a private repository
+
+Repository administrators can enable or disable the dependency graph for private repositories.
+
+You can also enable or disable the dependency graph for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.sidebar-settings }}
+{{ site.data.reusables.repositories.navigate-to-security-and-analysis }}
+4. Read the message about granting {{ site.data.variables.product.product_name }} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**.
+   !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
+
+You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
+{% endif %}
+
+### Troubleshooting the dependency graph
+
+If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
+
+{% if currentVersion == "free-pro-team@latest" %}
+If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a {{ site.data.variables.product.prodname_enterprise }} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
+
+If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
+
+### Further reading
+
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
+- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
+- "[Understanding how {{ site.data.variables.product.product_name }} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)"
+{% endif %}

content/github/visualizing-repository-data-with-graphs/index.md

@@ -0,0 +1,32 @@
+---
+title: Visualizing repository data with graphs
+redirect_from:
+  - /categories/44/articles/
+  - /categories/graphs-and-contributions/
+  - /categories/graphs/
+  - /categories/visualizing-repository-data-with-graphs
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+
+### Table of Contents
+
+{% topic_link_in_list /accessing-basic-repository-data %}
+    {% link_in_list /about-repository-graphs %}
+    {% link_in_list /viewing-a-summary-of-repository-activity %}
+    {% link_in_list /viewing-a-projects-contributors %}
+<!-- if currentVersion == "free-pro-team@latest" -->
+    {% link_in_list /viewing-traffic-to-a-repository %}
+<!-- endif -->
+{% topic_link_in_list /analyzing-changes-to-a-repositorys-content %}
+    {% link_in_list /visualizing-commits-in-a-repository %}
+    {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %}
+{% topic_link_in_list /understanding-connections-between-repositories %}
+    {% link_in_list /viewing-a-repositorys-network %}
+    {% link_in_list /listing-the-forks-of-a-repository %}
+<!-- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.16" -->
+    {% link_in_list /about-the-dependency-graph %}
+    {% link_in_list /exploring-the-dependencies-of-a-repository %}
+<!-- endif -->

content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md

@@ -0,0 +1,28 @@
+---
+title: Listing the forks of a repository
+intro: The Members graph displays all the forks of a repository.
+redirect_from:
+  - /articles/listing-the-forks-of-a-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+Forks are listed alphabetically by the username of the person who forked the repository. You can click on the username to be redirected to the user's {{ site.data.variables.product.product_name }} profile page or click on the fork name to be redirected to the specific fork of the repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Repository members graph](/assets/images/help/graphs/repo_forks_graph_dotcom.png)
+
+{% else %}
+
+![Repository members graph](/assets/images/help/graphs/repo_members_graph.png)
+
+{% endif %}
+
+### Accessing the Members graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Forks**.
+![Forks tab](/assets/images/help/graphs/graphs-sidebar-forks-tab.png)

content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md

@@ -0,0 +1,11 @@
+---
+title: Understanding connections between repositories
+intro: 'You can better understand the connections that exist between repositories by viewing a repository''s network{% if currentVersion == "free-pro-team@latest" %}, projects that depend on the repository,{% endif %} and its forks.'
+mapTopic: true
+redirect_from:
+  - /articles/understanding-connections-between-repositories
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+

content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md

@@ -0,0 +1,46 @@
+---
+title: Viewing a project's contributors
+intro: 'You can see who contributed commits to a repository{% if currentVersion == "free-pro-team@latest" %} and its dependencies{% endif %}.'
+redirect_from:
+  - /articles/i-don-t-see-myself-in-the-contributions-graph/
+  - /articles/viewing-contribution-activity-in-a-repository/
+  - /articles/viewing-a-projects-contributors
+product: '{{ site.data.reusables.gated-features.repository-insights }}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+### About contributors
+
+You can view the top 100 contributors to a repository{% if currentVersion != "free-pro-team@latest" %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
+{% endif %}
+
+### Accessing the contributors graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Contributors**.
+  ![Contributors tab](/assets/images/help/graphs/contributors_tab.png)
+4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected.
+  ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
+
+### Troubleshooting contributors
+
+If you don't appear in a repository's contributors graph, it may be because:
+- You aren't one of the top 100 contributors.
+- Your commits haven't been merged into the default branch.
+- The email address you used to author the commits hasn't been added to your {{ site.data.variables.product.product_name }} account.
+
+{% tip %}
+
+**Tip:** To list all commit contributors in a repository, see "[Repositories](/v3/repos/#list-contributors)."
+
+{% endtip %}
+
+If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/articles/about-pull-requests)."
+
+If the email address you used to author the commits has not been added to your {{ site.data.variables.product.product_name }} account, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)" and "[Adding an email address to your {{ site.data.variables.product.product_name }} account](/articles/adding-an-email-address-to-your-github-account)."

content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md

@@ -0,0 +1,26 @@
+---
+title: Viewing a repository's network
+intro: 'The network graph displays the branch history of the entire repository network, including branches of the root repository and branches of forks that contain commits unique to the network.'
+product: '{{ site.data.reusables.gated-features.repository-insights }}'
+redirect_from:
+  - /articles/viewing-a-repository-s-network
+  - /articles/viewing-a-repositorys-network
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+![Repository network graph](/assets/images/help/graphs/repo_network_graph.png)
+
+{% tip %}
+
+**Tip:** To see older branches, click and drag within the graph.
+
+{% endtip %}
+
+### Accessing the network graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Network**.
+![Network tab](/assets/images/help/graphs/network_tab.png)

content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md

@@ -0,0 +1,23 @@
+---
+title: Viewing a summary of repository activity
+intro: 'You can view an overview of a repository''s activity through Pulse. Pulse includes a list of open and merged pull requests, open and closed issues, and a graph showing the commit activity for the top 15 users who committed to the default branch of the project in the selected [time period](/articles/viewing-a-summary-of-repository-activity#filtering-by-time).'
+product: '{{ site.data.reusables.gated-features.repository-insights }}'
+redirect_from:
+  - /articles/viewing-a-summary-of-repository-activity
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+Commit co-authors are included in the commit activity summary if their commits were merged into the repository's default branch and they're in the top 15 users who have contributed the most commits.
+
+### Accessing pulse
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+
+### Filtering by time
+
+By default, Pulse shows the last seven days of repository activity. To choose a different time period, click the **Period** dropdown in the upper-right corner of the Pulse overview.
+
+![Filtering Pulse activity by time](/assets/images/help/pulse/pulse_time_filter_dropdown.png)

content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md

@@ -0,0 +1,28 @@
+---
+title: Viewing traffic to a repository
+intro: 'Anyone with push access to a repository can view its traffic, including full clones (not fetches), visitors from the past 14 days, referring sites, and popular content in the traffic graph.'
+product: 'This repository insights graph is available in public repositories with {{ site.data.variables.product.prodname_free_user }} and {{ site.data.variables.product.prodname_free_team }} for organizations, and in public and private repositories with {{ site.data.variables.product.prodname_pro }}, {{ site.data.variables.product.prodname_team }}, and {{ site.data.variables.product.prodname_ghe_cloud }}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{{ site.data.variables.product.prodname_dotcom }}''s products](/articles/github-s-products)."{% endif %}'
+redirect_from:
+  - /articles/viewing-traffic-to-a-repository
+versions:
+  free-pro-team: '*'
+---
+
+You can navigate to referring sites, excluding search engines and {{ site.data.variables.product.product_name }} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic.
+
+Referring sites and popular content are ordered by views and unique visitors. Full clones and visitor information update hourly, while referring sites and popular content sections update daily. All data in the traffic graph uses the UTC+0 timezone, regardless of your location.
+
+{% tip %}
+
+**Tip:** You can hover over a specific day in the traffic graph to view the exact data for that day.
+
+{% endtip %}
+
+![Repository traffic graphs with tooltip](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png)
+
+### Accessing the traffic graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Traffic**.
+![Traffic tab](/assets/images/help/graphs/traffic_tab.png)

content/github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository.md

@@ -0,0 +1,23 @@
+---
+title: Visualizing additions and deletions to content in a repository
+intro: The code frequency graph displays the content additions and deletions for each week in a repository's history.
+product: '{{ site.data.reusables.gated-features.repository-insights }}'
+redirect_from:
+  - /articles/visualizing-additions-and-deletions-to-content-in-a-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Code frequency graph](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png)
+
+{% endif %}
+
+### Accessing the code frequency graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Code frequency**.
+![Code frequency tab](/assets/images/help/graphs/code_frequency_tab.png)

content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md

@@ -0,0 +1,25 @@
+---
+title: Visualizing commits in a repository
+intro: You can see all commits made to a repository in the past year (excluding merge commits) in the Commit graph.
+product: '{{ site.data.reusables.gated-features.repository-insights }}'
+redirect_from:
+  - /articles/visualizing-commits-in-a-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+The top graph shows commits for the entire year by week.
+
+![Repository commit year graph](/assets/images/help/graphs/repo_commit_activity_year_graph.png)
+
+The bottom graph shows the average number of commits by day of the week for the selected week.
+
+![Repository commit week graph](/assets/images/help/graphs/repo_commit_activity_week_graph.png)
+
+### Accessing the commits graph
+
+{{ site.data.reusables.repositories.navigate-to-repo }}
+{{ site.data.reusables.repositories.accessing-repository-graphs }}
+3. In the left sidebar, click **Commits**.
+![Commits tab](/assets/images/help/graphs/commits_tab.png)