Add cross-links to common validation failure article - #14512
Add cross-links to common validation failure article#14512Nick Walker (nickwalkmsft) merged 6 commits into
Conversation
Relocate 'Common reasons for app validation failure' from post-publish section to before 'Submit your app' so developers can review common failures while preparing their submission. Fixes #14114 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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 5158a1d: ✅ Validation status: passed
For more details, please refer to the build report. |
This reverts commit 5158a1d.
Instead of moving the TOC entry, add cross-links between related articles so developers discover common validation failures while preparing their submission: - submission-checklist.md: added link to common-reasons article - teams-store-validation-guidelines.md: added link to common-reasons article - common-reasons-for-app-validation-failure.md: added link to submission checklist Fixes #14114 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
v-spakirla
changed the title
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 ff8de77: ✅ Validation status: passedFor more details, please refer to the build report. |
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 93bec97:
|
|
Learn Build status updates of commit 840f46e: ✅ Validation status: passedFor more details, please refer to the build report. |
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 |
3 participants
Summary
This PR adds cross-links between related articles so developers can discover common validation failures while preparing their submission.
Changes
Fixes #14114