Octomerger Bot
|
Before Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 101 KiB |
|
Before Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 9.0 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 8.8 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 8.0 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 81 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 40 KiB |
|
Before Width: | Height: | Size: 45 KiB |
|
Before Width: | Height: | Size: 5.8 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 63 KiB After Width: | Height: | Size: 71 KiB |
|
Before Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 172 KiB After Width: | Height: | Size: 51 KiB |
|
Before Width: | Height: | Size: 8.8 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 8.3 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 8.8 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 72 KiB |
BIN
assets/images/help/graphs/repo-commit-activity-graphs.png
Normal file
|
After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 5.5 KiB After Width: | Height: | Size: 46 KiB |
|
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 55 KiB |
|
Before Width: | Height: | Size: 87 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 114 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 147 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 8.9 KiB After Width: | Height: | Size: 12 KiB |
@@ -117,17 +117,12 @@ For more information, see "[Reviewing and fixing alerts](#reviewing-and-fixing-a
|
||||
{%- ifversion dependabot-bulk-alerts %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
1. Click the alert that you would like to view.{% ifversion dependabot-bulk-alerts %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
1. Click the alert that you would like to view.
|
||||
{% else %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-dependabot-alerts %}
|
||||
1. Click the alert you'd like to view.
|
||||
|
||||
{% endif %}{% ifversion dependabot-filter-label-security-advisory %}
|
||||
1. Click the alert you'd like to view.{% endif %}{% ifversion dependabot-filter-label-security-advisory %}
|
||||
1. Optionally, to suggest an improvement to the related security advisory, on the right-hand side of the alert details page, click **Suggest improvements for this advisory on the {% data variables.product.prodname_advisory_database %}**. For more information, see "[AUTOTITLE](/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database)."
|
||||
|
||||
|
||||
@@ -186,9 +181,9 @@ If you schedule extensive work to upgrade a dependency, or decide that an alert
|
||||
1. View the open {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts)".
|
||||
2. Optionally, filter the list of alerts by selecting a dropdown menu, then clicking the filter that you would like to apply. You can also type filters into the search bar.
|
||||
3. To the left of each alert title, select the alerts that you want to dismiss.
|
||||
|
||||
|
||||
4. Optionally, at the top of the list of alerts, select all alerts on the page.
|
||||
|
||||
|
||||
5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts.
|
||||
|
||||
|
||||
@@ -225,9 +220,8 @@ You can view all open alerts, and you can reopen alerts that have been previousl
|
||||
1. View the closed {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)" (above).
|
||||
2. To the left of each alert title, select the alerts that you want to reopen by clicking the checkbox adjacent to each alert.
|
||||
3. Optionally, at the top of the list of alerts, select all closed alerts on the page.
|
||||
|
||||
|
||||
4. Click **Reopen** to reopen the alerts. Alerts that have already been fixed cannot be reopened.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ The action is available for all {% ifversion fpt or ghec %}public repositories,
|
||||
|
||||
You can use the {% data variables.dependency-review.action_name %} in your repository to enforce dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository. For more information, see [`dependency-review-action`](https://github.com/actions/dependency-review-action).
|
||||
|
||||
|
||||
|
||||
|
||||
By default, the {% data variables.dependency-review.action_name %} check will fail if it discovers any vulnerable packages. A failed check blocks a pull request from being merged when the repository owner requires the dependency review check to pass. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ The dependency graph shows the dependencies{% ifversion fpt or ghec %} and depen
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
{% data reusables.repositories.click-dependency-graph %}{% ifversion fpt or ghec %}
|
||||
4. Optionally, under "Dependency graph", click **Dependents**.
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."
|
||||
@@ -48,15 +48,11 @@ Dependencies submitted to a project using the Dependency submission API (beta),
|
||||
|
||||
If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
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 {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.product_name %} does not populate the **Dependents** view.
|
||||
@@ -70,8 +66,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
## Enabling and disabling the dependency graph for a private repository
|
||||
|
||||
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
|
||||
|
||||
@@ -16,7 +16,7 @@ shortTitle: Access community profiles
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Community**.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -30,6 +30,6 @@ You can use discussions insights to help understand the contribution activity, p
|
||||
{% data reusables.repositories.navigate-to-repo %} For organization discussions, navigate to the main page of the source repository.
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Community**.
|
||||
|
||||
|
||||
1. Optionally, in the upper-right corner of the page, select the **Period** dropdown menu and click the time period for which you want to view data: **30 days**, **3 months**, or **1 year**.
|
||||
|
||||
|
||||
@@ -27,20 +27,16 @@ shortTitle: Analyze changes
|
||||
|
||||
You can see all commits made to a repository in the past year (excluding merge commits) in the Commit graph.
|
||||
|
||||
The top graph shows commits for the entire year by week.
|
||||
The top graph shows commits for the entire year by week. The bottom graph shows the average number of commits by day of the week for the selected week.
|
||||
|
||||
|
||||
|
||||
The bottom graph shows the average number of commits by day of the week for the selected week.
|
||||
|
||||
|
||||
|
||||
|
||||
### Accessing the commits graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Commits**.
|
||||
|
||||
|
||||
|
||||
## Visualizing additions and deletion to content in a repository
|
||||
|
||||
@@ -48,7 +44,7 @@ The code frequency graph displays the content additions and deletions for each w
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -57,4 +53,4 @@ The code frequency graph displays the content additions and deletions for each w
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Code frequency**.
|
||||
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ shortTitle: Connections between repositories
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -42,7 +42,7 @@ The network graph displays the branch history of the entire repository network,
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Network**.
|
||||
|
||||
|
||||
|
||||
## Listing the forks of a repository
|
||||
|
||||
@@ -50,22 +50,12 @@ 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 {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Accessing the Members graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Forks**.
|
||||
|
||||
|
||||
|
||||
## Viewing the dependencies of a repository
|
||||
|
||||
|
||||
@@ -30,9 +30,9 @@ You can also see a list of people who have contributed to the project's Python d
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Contributors**.
|
||||
|
||||
|
||||
4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
|
||||
|
||||
|
||||
|
||||
## Troubleshooting contributors
|
||||
|
||||
|
||||
@@ -31,4 +31,4 @@ Referring sites and popular content are ordered by views and unique visitors. Fu
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Traffic**.
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
3. In the left sidebar, click **Dependency graph**.
|
||||
|
||||
|
||||
|
||||