Merge pull request #11 from askpatrickw/patch-1

add write permissions to ADO PAT Docs

README.md

@@ -47,7 +47,7 @@ The recommendation is to use a GitHub App to run the migration - a GitHub app ha
 1. Create Private Key for GitHub App
 1. Obtain App ID and Installation ID - see [the instructions for using smee.io](https://josh-ops.com/posts/github-apps/#creating-a-github-app)
 1. Create the following action secrets:
-    + `ADO_PAT`: Azure DevOps PAT with appropriate permissions to read work items
+    + `ADO_PAT`: Azure DevOps PAT with appropriate permissions to read work and write items
     + `PRIVATE_KEY`: The contents of the private key created and downloaded in step #2
 1. Use the [action](.github/workflows/migrate-work-items.yml) and update the App ID and Installation ID obtained in step #3
 1. Update any defaults in the [action](.github/workflows/migrate-work-items.yml) (ie: Azure DevOps organization and project, GitHub organization and repo)
@@ -91,4 +91,4 @@ Using the GitHub app might be better so you don't reach a limit on your GitHub a
 | `-gh_assigned_to_user_suffix`   | No       | `""`     | Used in conjunction with `-gh_update_assigned_to`, used to suffix the username, e.g. if using GitHub Enterprise Managed User (EMU) instance |
 | `-gh_add_ado_comments`          | No       | `$false` | Switch to add ADO comments as a section with the migrated work item                                                                     |
 
-+ **Note**: With `-gh_update_assigned_to $true`, you/your users will receive a lot of emails from GitHub when the user is assigned to the issue
++ **Note**: With `-gh_update_assigned_to $true`, you/your users will receive a lot of emails from GitHub when the user is assigned to the issue