John Ericson 68c81c7375 Put functional tests in tests/functional ... I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```		2023-10-06 09:05:56 -04:00
..
ISSUE_TEMPLATE	docs issue template: move checklist down	2023-06-15 02:31:49 +02:00
workflows	Bump docker/login-action from 2 to 3	2023-09-18 22:16:55 +00:00
CODEOWNERS	Remove my CODEOWNER-ship to libstore	2023-02-22 09:10:24 +01:00
dependabot.yml	dependabot: automatically keep github actions up-to-date	2020-06-27 20:37:05 +01:00
labeler.yml	Put functional tests in tests/functional	2023-10-06 09:05:56 -04:00
PULL_REQUEST_TEMPLATE.md	remove maintainers checklist in PR template	2023-09-05 14:08:40 +02:00
STALE-BOT.md	throw freenode down the memory hole	2021-05-27 21:48:39 +02:00
stale.yml	update stale bot per RFC 0124	2022-07-10 16:50:49 -07:00