Skip to content

Commit d0bc4dc

Browse files
authored
Merge pull request #50038 from github/repo-sync
Repo sync
2 parents 697d150 + 1d6ffc1 commit d0bc4dc

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

content/code-security/getting-started/adding-a-security-policy-to-your-repository.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ shortTitle: Add a security policy
2020

2121
## About security policies
2222

23-
To give people instructions for reporting security vulnerabilities in your project, you can add a `SECURITY.md` file to your repository's root, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy.
23+
To give people instructions for reporting security vulnerabilities in your project, you can add a `SECURITY.md` file to your repository's root, `docs`, or `.github` folder. Adding this file to this part(s) of your repository automatically creates a row with a description where people can review it. When someone creates an issue in your repository, they will see a link to your project's security policy.
2424

2525
You can create a default security policy for your organization or personal account. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
2626

content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Discussion category forms | Discussion category forms customize the templates th
4747
_FUNDING.yml_ | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)."{% endif %}
4848
_GOVERNANCE.md_ | A GOVERNANCE file lets people know about how your project is governed. For example, it might discuss project roles and how decisions are made.
4949
Issue and pull request templates and _config.yml_ | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
50-
_SECURITY.md_ | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
50+
_SECURITY.md_ | A SECURITY file gives instructions on how to report a security vulnerability in your project and description that hyperlinks the file. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
5151
_SUPPORT.md_ | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project)."
5252

5353
You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.

data/reusables/community/issue-forms-sample.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
```yaml copy
22
name: Bug Report
3-
description: File a bug report
3+
description: File a bug report.
44
title: "[Bug]: "
55
labels: ["bug", "triage"]{% ifversion projects-in-issue-forms %}
66
projects: ["octo-org/1", "octo-org/44"]{% endif %}
@@ -59,7 +59,7 @@ body:
5959
id: terms
6060
attributes:
6161
label: Code of Conduct
62-
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)
62+
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com).
6363
options:
6464
- label: I agree to follow this project's Code of Conduct
6565
required: true

0 commit comments

Comments
 (0)