Skip to content

Document Windows-native command guidance#63

Open
caomengxuan666 wants to merge 1 commit into
microsoft:mainfrom
caomengxuan666:winuxcmd/windows-native-command-notes
Open

Document Windows-native command guidance#63
caomengxuan666 wants to merge 1 commit into
microsoft:mainfrom
caomengxuan666:winuxcmd/windows-native-command-notes

Conversation

@caomengxuan666

@caomengxuan666 caomengxuan666 commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add short notes for Windows-native command scope and option support
  • link the notes from CONTRIBUTING.md without changing README
  • document guidance from recent issue discussions so contributors have a clearer starting point when adding native commands

@lhecker lhecker requested a review from crutkas June 8, 2026 19:08
@crutkas

crutkas commented Jun 8, 2026

Copy link
Copy Markdown
Member

@caomengxuan666 can you explain a bit more why this is needed? this feels very AI driven from a wording stance and want to deeper understand the needs for this.

@caomengxuan666

Copy link
Copy Markdown
Contributor Author

I opened this because recent native-command PRs/issues like ps, kill, which, lsof, chown/chgrp all seem to run into the same discussion: should this command exist here, and what option scope is acceptable on Windows?

So I thought maybe it would be useful to leave a small contributor note saying: please discuss the scope first before opening a native-command PR.

But yeah, the current wording is probably too generic. Maybe I overdid it. I can trim it down a lot, or close this for now.

@lhecker lhecker added the E-needs-discussion Needs discussion between maintainers. label Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

E-needs-discussion Needs discussion between maintainers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants