Skip to content
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

Fix typo in about_Parsing.md #11207

Merged
merged 1 commit into from
Jun 24, 2024
Merged

Fix typo in about_Parsing.md #11207

merged 1 commit into from
Jun 24, 2024

Conversation

sethvs
Copy link
Contributor

@sethvs sethvs commented Jun 24, 2024

PR Summary

Add missing letter in about_Parsing.md

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Copy link
Contributor

Learn Build status updates of commit eabb0cc:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • [Error: CannotMergeCommit] Cannot merge commit eabb0ccff10dbb66d9dfbe949f6217a6033622fd in branch typo of repository https://github.com/sethvs/PowerShell-Docs into branch main (commit b0246898da471e08ffabc70991b8ec5266f81528). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

@sdwheeler
Copy link
Contributor

Your fork is out of sync. The 7.3 docs were removed over a month ago when support for 7.3 ended.

Copy link
Contributor

Learn Build status updates of commit d316051:

✅ Validation status: passed

File Status Preview URL Details
reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.2)
reference/7.4/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.4)
reference/7.5/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

@sdwheeler
Copy link
Contributor

I rebased your branch to resolve the merge conflict.

Copy link
Contributor

Learn Build status updates of commit e261d9a:

✅ Validation status: passed

File Status Preview URL Details
reference/7.2/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.2)
reference/7.4/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.4)
reference/7.5/Microsoft.PowerShell.Core/About/about_Parsing.md ✅Succeeded View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

@sdwheeler sdwheeler merged commit 6710ba1 into MicrosoftDocs:main Jun 24, 2024
4 checks passed
@sethvs sethvs deleted the typo branch June 24, 2024 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants