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
We are currently maintaining bot configs on the machine running infra cluster for community automations. This is not a good way to persistent configs, track changes, and not transparent to contributors who'd like to provide helps.
What to do
Create a separate repository for hosting bot/automation relevant tools.
Upload prow bot configs to the repo, and make the machine automatically clone and apply configs to running infrastructure envrionment.
We also need a clear folder setup (guide/instruction), to make it easy for hosting other configs in the long term.
The text was updated successfully, but these errors were encountered:
This have been open for a long period but no progress due to lack of volunteer.
We still want it as it helps transparency and neutrality of community infra management.
/label help-wanted
/cc @kubeedge/tsc @kubeedge/maintainers for sugguestions.
@kevin-wangzefeng: The label(s) /label help-wanted cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash
This have been open for a long period but no progress due to lack of volunteer.
We still want it as it helps transparency and neutrality of community infra management.
/label help-wanted
/cc @kubeedge/tsc @kubeedge/maintainers for sugguestions.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Background
e.g. Support config domain URL for cloudcore kubeedge#2126
What to do
Create a separate repository for hosting bot/automation relevant tools.
Upload prow bot configs to the repo, and make the machine automatically clone and apply configs to running infrastructure envrionment.
We also need a clear folder setup (guide/instruction), to make it easy for hosting other configs in the long term.
The text was updated successfully, but these errors were encountered: