-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Formatting and phrases #4946
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
Formatting and phrases #4946
Conversation
@Jay-o-Way : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
FYI @ethanfangg |
PRMerger Results
|
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.
Looks good overall. Just a couple of minor comments/suggestions. Thanks for going through all these pages.
Learn Build status updates of commit e738ec3: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. For any questions, please:
|
PRMerger Results
|
done :) |
Learn Build status updates of commit 7d3fa3e: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. For any questions, please:
|
PRMerger Results
|
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.
Looks great. Thanks again!
…c_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
Pretty similar to #4935.
A little bit related to https://github.com/microsoft/PowerToys/pull/32351/files. Release 0.81 is expected around MS Build (late May) but as there are only a handful changes which are in both the UI and in the Docs, I don't see a problem changing this now.