Skip to content

Support inline comment links in review workflows - #28

Merged
dkropachev merged 4 commits into
mainfrom
fix/code-quality-thread-links
Oct 24, 2026
Merged

dkropachev merged 4 commits into
mainfrom
fix/code-quality-thread-links

Conversation

@dkropachev

Copy link
Copy Markdown
Contributor

Issue

Review helpers rejected #discussion_rID links, preventing direct handling of inline findings such as this GitHub Code Quality comment.

Fix

Preserve inline comment links through fetching, reply validation, resolution, and resume. Select only the containing thread while retaining complete PR evidence as context; missing or ambiguous matches stop the workflow.

Keep request mappings and mutations within the original selection, reuse verified existing answers, and apply the ordinary guarded workflow to actionable bot findings. Synchronize both host manifests at version 1.1.19.

Review helpers rejected discussion_r links, preventing direct handling of
GitHub Code Quality findings. Preserve the comment selection through fetching,
reply validation, resolution, and resume without widening its thread scope.

Add regression coverage and synchronize plugin manifests at version 1.1.19.
Validated with scripts/check.py, scripts/test.py, and read-only checks against
the reported GitHub thread.
Completion snapshots only recognized reviewReference and silently lost the
selection for direct comment links. Forward either selection identity to the
shared selector so completion audits retain the same thread boundary and reject
missing or ambiguous comment matches.

Cover resolved-thread selections and invalid matches in completion audit tests.
The legacy GraphQL databaseId field is deprecated and does not guarantee
64-bit identifiers. Query fullDatabaseId for comments and submitted reviews
through stable aliases on both pagination paths. Normalize BigInt comment
strings to integers so existing snapshots and selection consumers keep their
current output contract.

Cover realistic large string and integer IDs, including paginated replies.
The pagination fixture returned BigInt values regardless of requested fields,
so reverting either query to legacy identifiers remained undetected. Check the
outgoing comment and review ID fields on every initial and nested request
before accepting the fixture response as coverage.

Verify all four field rollback mutations fail the strengthened test. Full
repository checks and tests pass, alongside live pagination verification.
@dkropachev
dkropachev merged commit 6841cb4 into main Oct 24, 2026
1 check passed
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