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
{{ message }}
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
Still thinking through this but the objective is to be able to configure one's bot instance to enable certain capabilities.
We can take our GitHub Events and then map those to URLs where the plugins are hosted.
I'm still unsure what capabilities we should leave in the bot kernel "local plugins" which will execute instantly.
My default answer is to break apart every handler into separate plugins and then move them back into the kernel only if theres a usability issue regarding its decreased speed.
header: "Thank you for contributing to UbiquiBot! Please be sure to set your wallet address before completing your first task so that the automatic payout upon task completion will work for you."
displayHelpMenu: true
footer: "###### Also please star this repository and [@ubiquity/devpool-directory](https://github.com/ubiquity/devpool-directory/) to show your support. It helps a lot!"
New Config
payments:
basePriceMultiplier: 1.5features:
newContributorGreeting:
enabled: trueheader: "Thank you for contributing to UbiquiBot! Please be sure to set your wallet address before completing your first task so that the automatic payout upon task completion will work for you."displayHelpMenu: truefooter: "###### Also please star this repository and [@ubiquity/devpool-directory](https://github.com/ubiquity/devpool-directory/) to show your support. It helps a lot!"handlers:
# issues.labeled: # in reality these should be disabled to fallback to be handled locally and instantly.# workflow: ubiquity/assistive-pricing# issues.unlabeled:# workflow: ubiquity/assistive-pricingissues.closed:
workflow: ubiquity/comment-incentivessettings: # intentionally using a different word than "config" to differentiate between bot and plugin configcomment:
elements:
code: 1img: 0h1: 1h2: 1h3: 1h4: 1h5: 1h6: 1li: 0.5a: 1blockquote: 0i: 0totals:
word: 0.1
Remarks
Technically speaking we can either create a single workflow to host multiple handlers, or to be more organized, we can make dedicated workflows/repositories per event handler.
Could be very interesting to follow the UNIX philosophy of small programs (plugins) that can pipe input and output for advanced interoperability. Imagine chaining ubiquity/comment-incentives and ubiquity/user-multiplier for example
It could also be useful to allow partner's to associate plugins with specific commands. That way projects can easily install their own slash commands. For example:
Events Example
https://github.com/ansible/webhooks.js-release/blob/6b8d9f69792bf16000cb609e649d31436ec528b5/dist-types/generated/webhook-names.d.ts#L1
Reference Config
ubiquibot/.github/ubiquibot-config.yml
Lines 1 to 8 in 3ee39e0
New Config
Remarks
Technically speaking we can either create a single workflow to host multiple handlers, or to be more organized, we can make dedicated workflows/repositories per event handler.
Could be very interesting to follow the UNIX philosophy of small programs (plugins) that can pipe input and output for advanced interoperability. Imagine chaining
ubiquity/comment-incentives
andubiquity/user-multiplier
for exampleIt could also be useful to allow partner's to associate plugins with specific commands. That way projects can easily install their own slash commands. For example:
ChatGPT generated example of a config for
issues.labeled
The text was updated successfully, but these errors were encountered: