Skip to content

Conversation

@StevenMaude
Copy link
Contributor

@StevenMaude StevenMaude commented Nov 10, 2022

In "Configuring private vulnerability reporting for a repository".

Why:

Fixes a typo.

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

The text:

creat issue

is corrected to:

create issue

Check off the following:

  • I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • For content changes, I have completed the self-review checklist.

In "Configuring private vulnerability reporting for a repository".
@github-actions
Copy link
Contributor

Thanks for submitting a PR to the GitHub Docs project!

In order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, see the documentation.

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

github-actions bot commented Nov 10, 2022

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md fpt
ghec
fpt
ghec

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

@cmwilson21
Copy link
Contributor

@StevenMaude Thanks so much for opening a PR! I'll get this triaged for review ⚡

@cmwilson21 cmwilson21 added ready to merge This pull request is ready to merge Merge-after-freeze content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review code security Content related to code security and removed triage Do not begin working on this issue until triaged by the team labels Nov 10, 2022
Copy link
Contributor

@cmwilson21 cmwilson21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this fix! ✨

@cmwilson21
Copy link
Contributor

@StevenMaude Great catch! Thanks for submitting this PR. I'll get this merged once all the tests are passing ⚡

@cmwilson21 cmwilson21 merged commit d778a3e into github:main Nov 10, 2022
@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

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

Labels

code security Content related to code security content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge waiting for review Issue/PR is waiting for a writer's review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants