-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate comments #184
Comments
@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
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. |
Duplicate #154 |
! 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 ubiquity-os-marketplace/text-conversation-rewards#113 (comment)
The text was updated successfully, but these errors were encountered: