Update seeking community processor
What does this MR do and why?
With the recent addition of the quick win triage processor quick win there is now some confusion with the previous Seeking community contributions processor Seeking community contributions. This MR updates the Seeking community contributions triage processor to match most of the quick win processor but without an issue weight requirement and without removing the label.
This will help create some consistency for writing implementation sections.
Describe in detail what your merge request does and why.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-