Thanks for sharing more details, @clintam! I’ll ask the team to consider this use-case and see if they have any thoughts. We’ll followup as soon as there’s any news.
I also wanted to ask a followup question on something you said:
So imagine our bot POSTs a comment on an issue. Then at some point in the future we realize that we want to change that comment (perhaps to reflect the latest status of a PR). In order to identify the previous comment, we can look though the comment text to find some expected content, but it would also be nice to ensure that we are only updating a comment that we (our bot user) actually created. Thus it would be nice to search for existing comments where the “user.id” property matches our bot’s user id.
To be honest, I’m not sure I understand why you’re searching for comments based on the user’s ID here. Instead, why aren’t you searching based on the ID of the comment itself? If you know you want to change a specific comment – then change that comment, and not just some comment that was authored by the same user and has the same content. Imagine a case where your bot created two comments with the same content. How would you know which to update?
Comment IDs are unique and using those to find comments you want to change seems like something you might consider. If you remember the ID of the comment, then you also know which user it was authored by because that can’t be modified (it’s not possible to change who authored a comment), so there’s no need to check the user ID.