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
As debated previously, it has been decided that we should be targeting development for the current installed workflow plugins and all worker plugins would need redeployed. I think workers are receiving a workflow update for automatic deployments already but not sure what branch was planned for it
As some branches are out of sync and have new config settings, I thought it safer to list and decide here.
It's okay to use any branch, but risky since lots of updates come in. For example, command-start-stop has issues on the development branch but runs fine on the main branch. I must say that I don't like using a dev branch as the production.
As debated previously, it has been decided that we should be targeting
development
for the current installed workflow plugins and all worker plugins would need redeployed. I think workers are receiving a workflow update for automatic deployments already but not sure what branch was planned for itAs some branches are out of sync and have new config settings, I thought it safer to list and decide here.
Workflows:
conversation-rewards
: probably lots, @gentlementlegen rfcuser-activity-watcher
:watch.optOut
=== repos to exclude from being watched, all watched by defaultautomated-merging
: nothing newWorkers:
/wallet
: nothing new/query
: nothing new/start
: nothing newassistive-pricing
: nothing newThe text was updated successfully, but these errors were encountered: