Skip to content

Commit d774873

Browse files
committed
docs: Minor wording tweaks
1 parent 393dd73 commit d774873

File tree

4 files changed

+14
-5
lines changed

4 files changed

+14
-5
lines changed

.github/CODEOWNERS

+1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
#####################
22
# Main global owner #
33
#####################
4+
45
*

.github/pull_request_template.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ Before creating a PR, run through this checklist and mark each as complete:
1010
- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md).
1111
- [ ] If applicable, I have added tests that prove my fix is effective or that my feature works.
1212
- [ ] If applicable, I have checked that any relevant tests pass after adding my changes.
13-
- [ ] I have updated any relevant documentation ([`README.md`](/README.md) and [`CHANGELOG.md`](/CHANGELOG.md)).
13+
- [ ] I have updated any relevant documentation ([`README.md`](/README.md) and/or [`CHANGELOG.md`](/CHANGELOG.md)).

CHANGELOG.md

+8
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,11 @@
33
## 1.0.0 (Month Date, Year)
44

55
Initial release of the NGINX template repository.
6+
7+
---
8+
9+
# Changelog
10+
11+
## 1.0.0 (Month Date, Year)
12+
13+
Initial release of this project.

CONTRIBUTING.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -19,22 +19,22 @@ Follow the instructions on the README's [Getting Started](/README.md#Getting-Sta
1919

2020
### Report a Bug
2121

22-
To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](/SECURITY.md).**
22+
To report a bug, open an issue on GitHub with the label `bug` using the available [bug report issue form](/.github/ISSUE_TEMPLATE/bug_report.yml). Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](/SECURITY.md).**
2323

2424
### Suggest a Feature or Enhancement
2525

26-
To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the available [feature request template](/.github/feature_request_template.md). Please ensure the feature or enhancement has not already been suggested.
26+
To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the available [feature request issue form](/.github/ISSUE_TEMPLATE/feature_request.yml). Please ensure the feature or enhancement has not already been suggested.
2727

2828
### Open a Pull Request (PR)
2929

3030
- Fork the repo, create a branch, implement your changes, add any relevant tests, and submit a PR when your changes are **tested** and ready for review.
3131
- Fill in the [PR template](/.github/pull_request_template.md).
3232

33-
**Note:** If you'd like to implement a new feature, please consider creating a [feature request issue](/.github/feature_request_template.md) first to start a discussion about the feature.
33+
**Note:** If you'd like to implement a new feature, please consider creating a [feature request issue](/.github/ISSUE_TEMPLATE/feature_request.yml) first to start a discussion about the feature.
3434

3535
#### F5 Contributor License Agreement (CLA)
3636

37-
F5 requires all external contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)) before any of their changes can be incorporated into an F5 Open Source repository.
37+
F5 requires all contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/f5-cla/.github/blob/main/docs/f5_cla.md)) before any of their changes can be incorporated into an F5 Open Source repository (even contributions to the F5 CLA itself!).
3838

3939
If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs.
4040

0 commit comments

Comments
 (0)