Skip to content

Update known-warnings baseline for PR #81#84

Merged
mattleibow merged 1 commit into
mainfrom
update-known-warnings-for-pr81
May 11, 2026
Merged

Update known-warnings baseline for PR #81#84
mattleibow merged 1 commit into
mainfrom
update-known-warnings-for-pr81

Conversation

@mattleibow

Copy link
Copy Markdown
Collaborator

Updates the known-warnings.csv baseline to include the 20 new xref-not-found warnings introduced by PR #81 (Fill API documentation placeholders).

Changes (1 file, counts only):

Warning Old count New count
GTKExtensions.xml: Gdk.RGBA 2 8
GTKExtensions.xml: Gdk.Rectangle 4 5
GTKExtensions.xml: Graphene.Point 1 4
GTKExtensions.xml: Graphene.Point3D 1 4
GTKExtensions.xml: Graphene.Rect 1 4
GTKExtensions.xml: Graphene.Size 1 4
SKPathBuilder.xml: SKPathBuilder.Dispose 1

Baseline: 63 → 64 unique rows, 120 → 140 total.

Merge this before PR #81 so the automerge workflow can proceed.

Add 20 new expected xref-not-found warnings introduced by the
documentation fill PR:
- GTKExtensions.xml: +6 Gdk.RGBA, +1 Gdk.Rectangle, +3 Graphene.Point,
  +3 Graphene.Point3D, +3 Graphene.Rect, +3 Graphene.Size
- SKPathBuilder.xml: +1 SkiaSharp.SKPathBuilder.Dispose (new file)

Baseline: 63 → 64 unique rows, 120 → 140 total.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 10539ba:

✅ Validation status: passed

File Status Preview URL Details
.github/known-warnings.csv ✅Succeeded

For more details, please refer to the build report.

@mattleibow mattleibow merged commit 7b2d953 into main May 11, 2026
2 of 3 checks passed
@mattleibow mattleibow deleted the update-known-warnings-for-pr81 branch May 11, 2026 18:20
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

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.

1 participant