-
Notifications
You must be signed in to change notification settings - Fork 95
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
Use generic example password #3336
Use generic example password #3336
Conversation
* Use one argument per line
The PR preview for 486b38d is available at theforeman-foreman-documentation-preview-pr-3336.surge.sh The following output files are affected by this PR: |
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.
Ack with just one non-blocking note: The previous example username also implied the need to have administrative privileges (admin
). At a quick glance, I don't see the need for these privileges mentioned anywhere else in the document so it makes me wonder whether you should document it (as a prerequisite?) now that you are replacing admin
with a generic My_User_Name
. (If you think it's not needed, that's perfectly okay with me.)
* Use one argument per line (cherry picked from commit 2a942ec)
* Use one argument per line (cherry picked from commit 2a942ec)
What changes are you introducing?
removing the example password "redhat" due to branding issues and consistency.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
consistency.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
we have both "last argument | next command" and "last argument \ \n | next command". Any preference?
Checklists
Please cherry-pick my commits into: