Ildar Iskhakov 1b7ada4315 Add database migrations linter (#1020) ... # What this PR does This PR adds [django-migration-linter](https://github.com/3YOURMIND/django-migration-linter) to keep database migrations backwards compatible - we can automatically run migrations and they are zero-downtime, e.g. old code can work with the migrated database - we can run and rollback migrations without worrying about data safety - OnCall is deployed to the multiple environments core team is not able to control See [django-migration-linter checklist](https://github.com/3YOURMIND/django-migration-linter/blob/main/docs/incompatibilities.md) for the common mistakes and best practices ## Which issue(s) this PR fixes ## Checklist - [ ] Tests updated - [ ] Documentation added - [ ] `CHANGELOG.md` updated --------- Co-authored-by: Joey Orlando <joey.orlando@grafana.com>		2023-02-06 16:01:37 +08:00
..
workflows	Add database migrations linter (#1020)	2023-02-06 16:01:37 +08: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	add precommit rules for markdown/json files (#915)	2022-12-01 14:26:54 +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