repo sync

content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md

@@ -15,6 +15,8 @@ topics:
 
 You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
 
+{% data reusables.dependency-review.dependency-review-enabled-ghes %}
+
 You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."

content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md

@@ -16,6 +16,8 @@ topics:
 
 {% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
 
+{% data reusables.dependency-review.dependency-review-enabled-ghes %}
+
 After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 {% ifversion ghes %}

content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md

@@ -28,6 +28,8 @@ topics:
 
 {% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
 
+{% data variables.product.prodname_dependabot %} is just one of many features available to harden supply chain security for {% data variables.location.product_location %}. For more information about the other features, see "[About supply chain security for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise)."
+
 ### About {% data variables.product.prodname_dependabot_alerts %}
 {% endif %}
 

data/reusables/dependency-review/dependency-review-enabled-ghes.md

@@ -0,0 +1,3 @@
+{% ifversion ghes %}
+After you enable the dependency graph, users will have access to the dependency review feature. {% data reusables.dependency-review.short-summary %} For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+{% endif %}

data/reusables/dependency-review/feature-overview.md

@@ -1,4 +1,4 @@
-Dependency review helps you understand dependency changes and the security impact of these changes at every pull request. It provides an easily understandable visualization of dependency changes with a rich diff on the "Files Changed" tab of a pull request. Dependency review informs you of:
+{% data reusables.dependency-review.short-summary %} It provides an easily understandable visualization of dependency changes with a rich diff on the "Files Changed" tab of a pull request. Dependency review informs you of:
 - Which dependencies were added, removed, or updated, along with the release dates.
 - How many projects use these components.
 - Vulnerability data for these dependencies.

data/reusables/dependency-review/short-summary.md

@@ -0,0 +1 @@
+Dependency review helps you understand dependency changes and the security impact of these changes at every pull request.

stylesheets/index.scss

@@ -8,6 +8,7 @@
 @import "@primer/css/alerts/index.scss";
 
 @import "extended-markdown.scss";
+@import "markdown-overrides.scss";
 @import "headings.scss";
 @import "images.scss";
 @import "shadows.scss";

stylesheets/markdown-overrides.scss

@@ -0,0 +1,24 @@
+// What might happens is that we have a DOM of
+//
+//   <div class="markdown-body">
+//     <div style="display: none">Note</div>
+//     <h2>Heading</h2>
+//     ...
+//
+// When this is the case, by default, that first <div> that is the first
+// gets the `margin-top: 0 !important` and not the first <h2>.
+// Generally, the reason this even exists is because <h2> (and <h3>) elements
+// are given extra margin-top so as to divide the article into sections
+// with some extra whitespace. That's fine, but we don't to start the
+// top of the page with too much whitespace. That's why @primer/css
+// has a solution for that. Just the problem that it fails then first
+// element isn't actually a heading.
+// Note we're also doing it for a possible <h3> being the first element.
+// See https://github.com/primer/css/issues/2303
+// See internal issue #2368
+.markdown-body {
+  > h2:first-of-type,
+  > h3:first-of-type {
+    margin-top: 0 !important;
+  }
+}