-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Update documentation for requisites #49962
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
Conversation
@garethgreenaway Could you please make sure the description of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description of require_any looks accurate.
@garethgreenaway Excellent, thanks for checking! |
@cachedout ping? I believe I resolved all of your concerns. Do you have any others? |
What does this PR do?
Organize and clean-up documentation.
A lot of the requisites didn't make sense to me and I struggled to understand why one would be chosen over the other because they mostly sounded the same. I tried to work through a layman explanation of what makes each requisite special.
I also attempted to consolidate repetitive explanations, remove overly-technical bits, and re-arrange things so they're easier to navigate.
Hopefully all of my changes are helpful and technically accurate, but added explanations are to the best of my comprehension, so review would be excellent.
Commits signed with GPG?
Yes