Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
> For me, the overhead for an individual app is prohibitive for handling the untriaged label. Here is a diagram that might help clarify this proposal for a GitHub App...
I think we need something like https://organizer.gitconsensus.com/#/
I opened https://github.com/opensearch-project/.github/issues/115
@CEHENKLE I think we want to document that branch protection is required when creating new repos, 10 repos don't
I don't think so. We still create labels manually all over the place. I think we need some central command/control for labels that is org-wide in which we make 1...
+1 @dlvenable, for version labels in OpenSearch and OpenSearch Dashboards we have been using meta as described here: https://github.com/opensearch-project/opensearch-plugins/blob/main/META.md#create-or-update-labels-in-all-plugin-repos, but it would be nice to automate that too with a...
Can we introduce automation for this? Maybe a bot that merges main to feature branches on demand that's not a PR?
Maybe automation could be making these PRs all the time? The problem is always that conflicts need resolving, and at some point a human has to do it.
@VachaShah care to comment with more information from the backport bot please?
@zelinh what does Whitesource need in terms of branch protection to work?