You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the thread doesn't seem to exist yet since there are 0 comments, and the documentation is less than crystal-clear:
When Utterances loads, the GitHub issue search API is used to find the issue associated with the page based on url, pathname or title. If we cannot find an issue that matches the page, no problem, utterances-bot will automatically create an issue the first time someone comments.
It looks like there are six different configuration options, and no (documented) way to tell which one the owner of a given repo has chosen:
Blog Post ↔️ Issue Mapping
Choose the mapping between blog posts and GitHub issues.
Meaning I'm stuck just blindly trying to create a new issue with the syntax of an existing one, hoping that the configuration hasn't unluckily changed between now and then, and also hoping that Utterances will pick up threads that were not created by it and also not created by the owner of the repo.
The text was updated successfully, but these errors were encountered:
Of course, I could just "sign in" and create the thread, but "act on my behalf" is an extremely inappropriate permission that I just can't grant.
I want to post a particular comment on a particular thread at a particular time while I supervise; I'm not giving a 3rd-party service permission to post unlimited comments in unlimited locations indefinitely and unsupervised.
I'm trying to post a comment here:
https://www.pypy.org/posts/2023/12/pypy-v7314-release.html#utterances-thread
But the thread doesn't seem to exist yet since there are 0 comments, and the documentation is less than crystal-clear:
It looks like there are six different configuration options, and no (documented) way to tell which one the owner of a given repo has chosen:
Meaning I'm stuck just blindly trying to create a new issue with the syntax of an existing one, hoping that the configuration hasn't unluckily changed between now and then, and also hoping that Utterances will pick up threads that were not created by it and also not created by the owner of the repo.
The text was updated successfully, but these errors were encountered: