Add commentType to createComment and createThread methods#1370
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
dpaquette
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the way comments are created in pull request threads by explicitly setting the
commentTypefield to1when creating comments and threads. This ensures that comments are consistently recognized as standard comments by the API. Related tests have also been updated to verify the new behavior.API integration updates:
commentType: 1to the payload when creating comments withgitApi.createCommentinsrc/tools/repositories.ts, ensuring the comment type is explicitly set.commentType: 1to each comment in the payload when creating threads withgitApi.createThreadinsrc/tools/repositories.ts.Test updates:
test/src/tools/repositories.test.tsto expectcommentType: 1in the payloads for bothcreateCommentandcreateThreadcalls, ensuring tests accurately reflect the new API usage. [1] [2] [3] [4] [5] [6] [7]GitHub issue number
#1368
Associated Risks
N/A
✅ PR Checklist
🧪 How did you test it?
updated automated tests, all are passing