Jean Boussier 6b446bee63 Remove SQLite production warning but leave production config disabled ... There are valid use cases for running SQLite in production, however it must be done with care, so instead of a warning most users won't see anyway, it's preferable to leave the configuration commented out to force them to think about having the database on a persistent volume etc. Co-Authored-By: Jacopo Beschi <beschi.jacopo@gmail.com>		2023-12-27 23:32:18 +01:00
..
workflows	Remove SQLite production warning but leave production config disabled	2023-12-27 23:32:18 +01:00
autolabeler.yml	Label Action Text PRs [ci skip]	2019-01-04 23:48:30 -05:00
CODEOWNERS	Add myself of codeowner of the rubocop config	2019-12-09 12:42:06 -03:00
issue_template.md	[ci skip] Mention executable test cases in issue template	2021-06-01 11:51:31 -07:00
no-response.yml	Changed wording for no-response documentation	2018-10-20 00:49:49 -04:00
pull_request_template.md	Clarify CI requirement in PR template [ci skip]	2022-12-02 11:04:05 -06:00
security.md	Typo in the Security Policy URL	2021-12-15 23:10:39 -05:00
stale.yml	Update stale issue comment to mention 7-1-stable	2023-10-09 16:20:04 +09:00
verba-sequentur.yml	Add verba-sequentur configuration [ci-skip]	2020-05-25 01:02:20 -05:00