oncall-engine/.github
Joey Orlando a44bd31e94
add new bug and feature-request GitHub Issue templates (#2230)
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.
2023-06-15 09:25:10 -04:00
..
ISSUE_TEMPLATE add new bug and feature-request GitHub Issue templates (#2230) 2023-06-15 09:25:10 -04:00
workflows add new bug and feature-request GitHub Issue templates (#2230) 2023-06-15 09:25:10 -04:00
CODEOWNERS tag @grafana/docs-oncall instead of oncall-backend for docs related changes (#1251) 2023-01-31 09:34:29 +01:00
issue_and_pr_commands.json add precommit rules for markdown/json files (#915) 2022-12-01 14:26:54 +01:00
pull_request_template.md update pr template (#1610) 2023-03-23 11:48:33 +01:00
verify-public-docs-updated.sh add small script + github action to check that public docs updated (#1177) 2023-01-20 13:23:06 +01:00