Skip to content

Conversation

@VimalaMoger
Copy link
Contributor

Document url:
https://docs.github.com/en/code-security/getting-started/quickstart-for-securing-your-repository

Why:

Managing dependency review section

There were some redundant lines

What's being changed (if available, include any code snippets, screenshots, or gifs):

Eliminated them and added a new line

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 14, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 14, 2025

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
code-security/getting-started/quickstart-for-securing-your-repository.md fpt
ghec
ghes@ 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.18 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

Removed this line: enable {% data variables.product.prodname_GH_code_security %}

I don't think it exists.
@Sharra-writes
Copy link
Contributor

@VimalaMoger Thanks for opening a PR! The thing about that second edit is that the lines you're removing are versioned. I can't check to make sure they're actually redundant, because I'm not an enterprise, and I'm generally reluctant to touch versioning. The first change seems reasonable. The second I don't think we can accept.

@Buffalo456

This comment was marked as spam.

@VimalaMoger
Copy link
Contributor Author

Thanks for the update.

@VimalaMoger
Copy link
Contributor Author

Please accept the one that is right for you. Thanks for clarifying that!

@Sharra-writes Sharra-writes added this pull request to the merge queue Oct 15, 2025
Merged via the queue into github:main with commit 97ba664 Oct 15, 2025
40 checks passed
@github-actions
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

@VimalaMoger VimalaMoger deleted the bugFix## branch October 16, 2025 20:53
@1234jlinkst-cloud
Copy link

1234jlinkst-cloud commented Oct 17, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants