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
windows/*: add page #8783
windows/*: add page #8783
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
…markdown, resolve-path
…, test-json, wait-process
|
I think I'm done for now. |
|
Hey @fcrespo82, thanks for your engagement. Unfortunately we always have to reject suggestions concerning the structure of the pages. There are so much different clients by now and every one of them is maintained by someone else. Changing the directory structure would break all those clients and it's impossible to ensure, that every one gets updated to meet the new specification. |
|
Sorry, I though this PR was about adding this new Edit: Such big PRs like this can take some time to be reviewed, especially now during Hacktober, just fyi. |
|
Sorry for the confusion. I did mention the change of structure in the PR, but not changed anything without consent. This is still only adding pages. I appreciate the effort to review the PR. Thanks again for the tool. |
|
Update: I updated the PR description to refer to Issue #6621 by @reinhart1010. I didn't use |
|
@navarroaxel I made all suggested changes. Thanks for the review. |
Co-authored-by: Axel Navarro <navarroaxel@gmail.com>
|
The build for this PR failed with the following error(s): Please fix the error(s) and push again. |
Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
|
Hi all! This thread has not had any recent activity. |
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.
This is good enough.
common,linux,osx,windows,sunos,android, etc.Thanks for this amazing project. Many times I needed to know how to run a command but the help/manpage was too complex.
I'm still working on adding more commands to this PR. Please hold from verifying until done.
Question: I noticed that some PowerShell related aliases have the same name of other tools. Is it possible to group utility related commands in a sub folder for disambiguation?
eg:
For #6621