Skip to content
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

Closed
0x4007 opened this issue Oct 31, 2024 · 5 comments
Closed

Consolidate comments #184

0x4007 opened this issue Oct 31, 2024 · 5 comments

Comments

@0x4007
Copy link
Member

0x4007 commented Oct 31, 2024

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.

A new workroom has been created for this task. Join chat

Originally posted by @ubiquity-os-beta in ubiquity-os-marketplace/text-conversation-rewards#113 (comment)

@0x4007
Copy link
Member Author

0x4007 commented Oct 31, 2024

@UbiquityOS find me more info and provide the links to the full conversation contexts where this idea mentioned in the spec was already discussed.

Copy link

! Error: HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment

Copy link

The ideas outlined in Specification #184 regarding plugin comments and appending them to the /start message have been previously discussed in the following conversations:

  1. Pull Request chore: rebrand #124
    Discussion on migrating logger packages and updating configuration files related to plugins.
    View PR #124 Conversation

  2. Issue Rebrand ubiquibot-config to ubiquity-os #83
    Conversation about renaming configuration files and setting up organization-level configurations for plugins.
    View Issue #83 Conversation

  3. Issue chore: added test types and test for configuration #55
    Discussion on implementing modules responsible for posting comments within the kernel, which relates to plugin interactions.
    View Issue #55 Conversation

  4. Issue Merge develop into main #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.

@0x4007
Copy link
Member Author

0x4007 commented Oct 31, 2024

Duplicate #154

Copy link

! Error: HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment

@0x4007 0x4007 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant