a44bd31e94
This is how `grafana/grafana` handles [bug reports](https://github.com/grafana/grafana/issues/new?assignees=&labels=&projects=&template=0-bug-report.yaml&title=Product-Area-Here%3A+short+description+of+bug+here) (for feature requests they have an [external link](https://github.com/grafana/grafana/issues/new/choose) pointing people to head over to their repo's Discussion page). This _should_ solve the problem of people opening new issues without properly filling in all the necessary information. Because users that are not a part of the `grafana` GitHub organization, do not have permission to add labels, this also solves that by automatically adding either the "bug" or "feature request" label based on which issue template they choose to use. |
||
|---|---|---|
| .. | ||
| helm_release.yml | ||
| helm_release_pr.yml | ||
| issue_commands.yml | ||
| linting-and-tests.yml | ||
| on-issue-creation.yml | ||
| on-issue-labeled.yml | ||
| publish-technical-documentation-next.yml | ||
| publish-technical-documentation-release.yml | ||
| snyk.yml | ||
| triage-stale-pull-requests.yml | ||
| verify-changelog-updated.yml | ||
| verify-public-docs-updated.yml | ||