generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 120
feat: Transfer content from docs repository #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
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
c0fcb1e
to
18f6bcf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 theCONTRIBUTING_DOCS.md
file.Checklist
Before creating a PR, run through this checklist and mark each as complete.
I have read the contributing guidelines.
I have signed the F5 Contributor License Agreement (CLA).
If applicable, I have added tests that prove my fix is effective or that my feature works.
If applicable, I have checked that any relevant tests pass after adding my changes.
I have updated any relevant documentation, such as (
README.md
andCHANGELOG.md
).I have rebased my branch onto main
I will ensure my PR is targeting the main branch and pulling from my branch from my own fork
If the change involves:
<username>
in place of PIIIn these cases, the change will require at least two (2) approvals before merging.