mirror of
https://github.com/grafana/grafana.git
synced 2024-11-22 08:56:43 -06:00
7295573e2e
* add new scenario to config * make workflow run on opened issues * revert-dont run on opened * action for newly opened issues * move new action config * remove opened from commands * change name * Update .github/workflows/issue-opened.yml ty! Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com> * make comment clearer --------- Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com>
10 lines
867 B
JSON
10 lines
867 B
JSON
[
|
|
{
|
|
"type": "author",
|
|
"memberOf": { "org": "grafana" },
|
|
"noLabels": true,
|
|
"addLabel": "internal",
|
|
"comment": " please add one or more appropriate labels. Here are some tips:\r\n\r\n- if you are making an issue, TODO, or reminder for yourself or your team, please add one label that best describes the product or feature area. Please also add the issue to your project board. :rocket:\r\n\r\n- if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one label that best describes the product or feature that you are discussing (e.g. `area/alerting`, `datasource/loki`, `type/docs`, `type/bug`, etc). [Our issue triage](https://github.com/grafana/grafana/blob/main/ISSUE_TRIAGE.md#3-categorizing-an-issue) doc also provides additional guidance on labeling. :rocket:\r\n\r\n Thank you! :heart:"
|
|
}
|
|
]
|