Update spe MigrationAPI - #11020
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit afba5db:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| [docs/embedded/build/Migrate content into SharePoint Embedded.md](https://github.com/Spucelik/sp-dev-docs/blob/update-spe-MigrationAPI/docs/embedded/build/Migrate content into SharePoint Embedded.md) | View | Details |
[docs/embedded/build/Migrate content into SharePoint Embedded.md](https://github.com/Spucelik/sp-dev-docs/blob/update-spe-MigrationAPI/docs/embedded/build/Migrate content into SharePoint Embedded.md)
- Line 0, Column 0: [Warning: filename-invalid-character - See documentation]
Only lowercase letters, numbers, and hyphens are allowed in filenames. - Line 0, Column 0: [Suggestion: filename-incomplete - See documentation]
The filename contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
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.
|
Adding Troy Starr (@TroyStarr) to review. |
|
Thanks Steve Pucelik (@Spucelik), I'll take a look. |
Andrew Connell (andrewconnell)
left a comment
There was a problem hiding this comment.
Steve Pucelik (@Spucelik) There are a few things you must fix before this PR, in addition to the inline commit for the page title:
- rename this file to meet the msdocs requirements (see the build warnings)
- this page doesn't appear linked to from any other page or the toc & thus is currently orphaned... it should be linked from somewhere, minimally the TOC
| @@ -0,0 +1,388 @@ | |||
| --- | |||
| title: Migrate content with the migration API | |||
There was a problem hiding this comment.
Title should be descriptive to say this is about SPE... the current title isn't descriptive enough
Category
What's in this Pull Request?
Guidance on how to use the Migration API. Details collected from the SPE Migration team and conversations that I have saved with them and customers.