Contributing
Join our community on Discord to discuss the development of devenv
.
When contributing, please note that smaller pull requests have a higher chance of being accepted, and pull requests with tests will be prioritized.
We have a rule that new features need to come with documentation and tests (devenv-run-tests
) to ensure the project stays healthy.
Preparing the devenv
development environment
-
Follow the installation instructions for Nix and Cachix.
-
git clone https://github.com/cachix/devenv.git
-
cd devenv
-
To build the project, run
nix-build
. -
./result/bin/devenv shell
-
Once you have made changes, run
./result/bin/devenv shell
again.
To automate this workflow, install and use direnv.
Repository structure
- The
devenv
CLI is insrc/devenv.nix
. - The
flake.nix
auto-generation logic lies insrc/flake.nix
. - All modules related to
devenv.nix
are insrc/modules/
. - Examples are automatically tested on CI and are the best way to work on developing new modules, see
examples/
. - Documentation is in
docs/
. - To run a development server, run
devenv up
.
Contributing language improvements
Language integration happens in stages. We welcome even the most basic support for getting started.
The most basic language support starts with the languages.*.enable
flag, which turns on basic tooling.
For an example, see src/modules/languages/elm.nix
.
The next step is to make the tooling customizable, so the versions can be overridden.
Most languages will come with either a languages.*.package
or languages.*.packages
option that allows the user to customize what version or package of the language they want to pick.
A further step is to provide languages.*.version
option, which allows the user to specify the exact version of the language.
For an example, see src/modules/languages/rust.nix
.