nix/.github/labeler.yml

"documentation":
  - doc/manual/*
  - src/nix/**/*.md

"store":
  - src/libstore/store-api.*
  - src/libstore/*-store.*

"fetching":
  - src/libfetchers/**/*

"repl":
  - src/libcmd/repl.*
  - src/nix/repl.*

"new-cli":
  - src/nix/**/*

"with-tests":
  # Unit tests
  - src/*/tests/**/*
  # Functional and integration tests
  - tests/functional/**/*
add labeler workflow 2022-03-30 10:45:28 -04:00			`"documentation":`
			`- doc/manual/*`
			`- src/nix/*/.md`

Try auto-labeling a few more things 2023-04-02 23:11:21 -04:00			`"store":`
			`- src/libstore/store-api.*`
			`- src/libstore/-store.`

			`"fetching":`
			`- src/libfetchers/*/`

			`"repl":`
			`- src/libcmd/repl.*`
			`- src/nix/repl.*`

			`"new-cli":`
			`- src/nix/*/`

labeler.yml: tests -> with-tests 2023-06-30 09:10:07 -04:00			`"with-tests":`
Try auto-labeling a few more things 2023-04-02 23:11:21 -04:00			`# Unit tests`
			`- src//tests//`
			`# Functional and integration tests`
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-05 12:12:18 -04:00			`- tests/functional/*/`