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
dnf: add and reorder examples #4063
Conversation
sudo not needed for search and other queries
Although `provides` can search the 'provides' metadata of packages, it's most commonly going to be used to search for specific files DNF manual also refers to it as 'file', see <https://dnf.readthedocs.io/en/latest/command_ref.html#provides-command>
Put commands that new users are more likely to use at the top, and in a logical flow (search > info > install).
Co-authored-by: Zlatan Vasović <zlatanvasovic@gmail.com>
I signed the CLA an hour ago. |
The build for this PR failed with the following error(s):
Please fix the error(s) and push again. |
The build for this PR failed with the following error(s):
Please fix the error(s) and push again. |
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.
Hey, thanks @jn64! I've left a really minor comment below for you to review. It's pretty much as-is though, so I'm approving :-)
Your issue with the CLAAssistant might be because you committed using an email address that isn't associated with your GitHub account. CLAAssisstant needs you to commit with email addresses that are associated with your GitHub account. You can also add the additional email address to your GitHub account, and this will fix the issue too :-)
Thanks again for the great contribution! This is certainly a huge improvement to this page :D
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.
Great job @jn64 and welcome to the project
@sbrl These commits were made on GitHub web, as you can see on the Verified tags on each commit, so the email is most definitely associated. However I'm using GitHub's private email option. I don't know how CLAassistant handles that. edit: it was an issue with cookies on CLAa which I've resolved. |
Co-authored-by: Starbeamrainbowlabs <sbrl@starbeamrainbowlabs.com>
common/
,linux/
, etc.)