Add manual triage to pipeline
What does this MR do?
It adds two manual jobs to the pipeline. One is for activating the issue triage manually. The other is for testing the issue triage. It contains --dry-run
which only simulates issue triage.
These hopefully simplify debugging why the issue triage does not work.
Inspired by https://about.gitlab.com/handbook/marketing/strategic-marketing/getting-started/105/.
How confident are you it won't break things if deployed?
98%
Links to related issues
How to test
Not testable as it is only a change in the pipeline.
Screenshots (if applicable)
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
used "state:" labels to track this MR's state until it was beta tested -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md
-
added a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing". - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.
Release notes text in German
Edited by Thomas