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

Deploy and dispatch using development #13

Open
7 tasks
Keyrxng opened this issue Sep 2, 2024 · 1 comment
Open
7 tasks

Deploy and dispatch using development #13

Keyrxng opened this issue Sep 2, 2024 · 1 comment

Comments

@Keyrxng
Copy link
Member

Keyrxng commented Sep 2, 2024

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.

Workflows:

  • conversation-rewards: probably lots, @gentlementlegen rfc
  • user-activity-watcher: watch.optOut === repos to exclude from being watched, all watched by default
  • automated-merging: nothing new

Workers:

  • /wallet: nothing new
  • /query: nothing new
  • /start: nothing new
  • assistive-pricing: nothing new
@gentlementlegen
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants