Transfer content #29
Merged
Transfer content #29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds the DocOps engineering team to CODEOWNERS, which should automatically tag them when requests affect the .github folder. There are other specific files or folders they could likely be added to (such as the Makefile), but this should do for now given the frequency of GitHub Action development.
- Config Sync Groups - Events - Settings
- Expose certificates endpoints for publication
Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>
Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>
Add fossa action. This is a copy of the implementation from the NIC repo. `FOSSA_TOKEN` secret has already been added to the repo. Co-authored-by: Alan Dooley <a.dooley@f5.com>
- Need doc follow-up to describe the feature
### Proposed changes Remove fossa while awaiting correct token ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [ ] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [ ] I have viewed my changes in the documentation Deploy Preview - [ ] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [ ] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [ ] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [ ] Review the doc for spelling errors. - [ ] Verify that all links in the doc work. - [ ] Verify that the doc follows the appropriate content template. - [ ] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [ ] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack.
### Proposed changes Add fossa and mend with workflow_dispatch only ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [x] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [x] I have viewed my changes in the documentation Deploy Preview - [x] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [x] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [x] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [x] Review the doc for spelling errors. - [x] Verify that all links in the doc work. - [x] Verify that the doc follows the appropriate content template. - [x] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [x] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack.
### Proposed changes Use correct secret names ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [ ] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [ ] I have viewed my changes in the documentation Deploy Preview - [ ] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [ ] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [ ] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [ ] Review the doc for spelling errors. - [ ] Verify that all links in the doc work. - [ ] Verify that the doc follows the appropriate content template. - [ ] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [ ] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack.
### Proposed changes Fix some broken links. Previous content now gone from Azure due to purge. ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [ ] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [ ] I have viewed my changes in the documentation Deploy Preview - [ ] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [ ] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [ ] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [ ] Review the doc for spelling errors. - [ ] Verify that all links in the doc work. - [ ] Verify that the doc follows the appropriate content template. - [ ] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [ ] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack.
### Proposed changes Update NIM catalog data to 2.18 release. Copied from NIM `release-2.18.0` branch. ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [x] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [x] I have viewed my changes in the documentation Deploy Preview - [x] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [x] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [x] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [x] Review the doc for spelling errors. - [x] Verify that all links in the doc work. - [x] Verify that the doc follows the appropriate content template. - [x] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [x] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack. --------- Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> Co-authored-by: Mike Jang <mi.jang@f5.com>
### Proposed changes This PR: - Adds bold to "deprecated" notice for SLES 12 SP5 on R33 <img width="956" alt="image" src="https://github.com/user-attachments/assets/87e37e82-446c-477a-810f-ddc74079330e" />
### Proposed changes Need to add a newly invalid 3rd party URL to the linkchecker ignore list. This is only used as an example and not an actual product link for users. (Similar to www.example.com) ### Checklist Before creating a PR, run through this checklist and mark each step as complete. - [ ] I have read the [`CONTRIBUTING`](https://github.com/nginxinc/docs/blob/main/CONTRIBUTING.md) document - [ ] I have viewed my changes in the documentation Deploy Preview - [ ] My PR is targeting the correct branch: - main: content that can be released immediately - product release branch: content that should be held for a future release - [ ] I have updated any relevant supporting documentation ([`README.md`](https://github.com/nginxinc/docs/blob/main/README.md) and the [`CHANGELOG.md`](https://github.com/nginxinc/docs/blob/main/CHANGELOG.md)) - [ ] I have followed the [conventional commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) for all commits on my branch When you're ready to merge a PR, run through this checklist and mark each step as complete. - [ ] Review the doc for spelling errors. - [ ] Verify that all links in the doc work. - [ ] Verify that the doc follows the appropriate content template. - [ ] Add technical and docs reviewers. Refer to the appropriate CODEOWNERS file, which includes authorized teams of reviewers. - [ ] Share the PR for review in the [`#nginx-doc-reviews`](https://f5.enterprise.slack.com/archives/C04PYFULN91) channel in Slack.
### Proposed changes This PR: - Adds linebreaks to commands for better human readability and to fix scrolling issues - Removes tabs in code blocks that impair the page layout
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
We're in the process of transferring most of our doc content to this repository, which will soon be publicly visible. (The remaining doc content is already available in other publicly visible open source repositories.)
This PR transfers that content.
In this PR, we'll test the build, to make sure what we see here is identical to what we see in our current internal repository.
After this PR is merged, I'll next address an internal issue where we'll "anonymize" the commits and committers to this repository. I'll then include an explanation of what we've done in the CONTRIBUTING.md file.
For the record, I cannot sign the F5 Contributor License Agreement until after we open this repository to the public. So that job will fail, and that's acceptable.
I've confirmed that the build works "locally" per the make commands described in the CONTRIBUTING_DOCS.md file.