Closed 0x4007 closed 2 weeks ago
@UbiquityOS find me more info and provide the links to the full conversation contexts where this idea mentioned in the spec was already discussed.
! Error: HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
The ideas outlined in Specification #184 regarding plugin comments and appending them to the /start
message have been previously discussed in the following conversations:
Pull Request #124
Discussion on migrating logger packages and updating configuration files related to plugins.
View PR #124 Conversation
Issue #83
Conversation about renaming configuration files and setting up organization-level configurations for plugins.
View Issue #83 Conversation
Issue #55
Discussion on implementing modules responsible for posting comments within the kernel, which relates to plugin interactions.
View Issue #55 Conversation
Issue #79
Conversation focusing on relevance scoring for review comments, which ties into how plugins might handle and evaluate different types of comments.
View Issue #79 Conversation
These links provide comprehensive context and details on how the plugin functionalities and related configurations have been addressed in past discussions. Reviewing these conversations will offer valuable insights and background information pertinent to Specification #184.
! Error: HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
Great example of a plugin comment that should be inside of the /start message.
I envision it can just append this below the /start table basically.
Make it so plugins can append if ran in a chain. This was discussed before by leveraging KV run ID in the metadata and such.
Originally posted by @ubiquity-os-beta in https://github.com/ubiquity-os-marketplace/text-conversation-rewards/issues/113#issuecomment-2449421593