-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Powertoys Run ValueGenerator docs #4509
Powertoys Run ValueGenerator docs #4509
Conversation
@IHorvalds : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit c1fbff9: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
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. Approving to publish with the 0.72.0 release.
Thank you! :) |
@alvinashcraft Hey, it seems I made a mistake in the formatting in this section: |
@IHorvalds Good catch. I can go try to fix it up quickly. |
It looks right in the GitHub preview: |
It looks fine in my VS Code preview pane too. I'm going to try adding a line break after "Examples:" and push to my branch. I can preview on the internal docs site with the windows-dev-docs-pr repo. |
It looks good on the review site in my branch after adding some line breaks. I'll get a PR merged ASAP. |
That's awesome! Thank you! |
You're welcome. The table should be rendering on the live site now. 😊 |
…c_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
This PR is in reference to microsoft/PowerToys#26097.