Project: lxd (Runtime / Container Runtime)
File: CONTRIBUTING.md

% Include content from ```{include} ../CONTRIBUTING.md :start-after: <!-- Include start contributing --> :end-before: <!-- Include end contributing --> ``` Follow the steps below to set up your development environment to get started working on new features for Incus. To build the dependencies, follow the instructions in {ref}`installingfromsource`. After setting up your build environment, add your GitHub fork as a remote: git remote add myfork git@github.com:<your_username>/incus.git git remote update Then switch to it: git checkout myfork/main Finally, you should be able to run `make` inside the repository and build your fork of the project. At this point, you most likely want to create a new branch for your changes on your fork: ```bash git checkout -b [nameofyournewbranch] git push myfork [nameofyournewbranch] ``` Persistent data is stored in the `INCUS_DIR` directory, which is generated by `incus admin init`. The `INCUS_DIR` defaults to `/var/lib/incus`. As you develop, you may want to change the `INCUS_DIR` for your fork of Incus so as to avoid version conflicts. Binaries compiled from your source will be generated in the `$(go env GOPATH)/bin` directory by default. You will need to explicitly invoke these binaries (not the global `incusd` you may have installed) when testing your changes. You may choose to create an alias in your `~/.bashrc` to call these binaries with the appropriate flags more conveniently. If you have a `systemd` service configured to run the Incus daemon from a previous installation of Incus, you may want to disable it to avoid version conflicts. We want Incus to be as easy and straight-forward to use as possible. Therefore, we aim to provide documentation that contains the information that users need to work with Incus, that covers all common use cases, and that answers typical questions. You can contribute to the documentation in various different ways. We appreciate your contributions! Typical ways to contribute are: Add or update documentation for new features or feature improvements that you contribute to the code. We'll review the documentation update and merge it together with your code. Add or update documentation that clarifies any doubts you had when working with the product. Such contributions can be done through a pull request or through a post in the section on the

New tutorials will be considered for inclusion in the docs (through a link or by including the actual content). To request a fix to the documentation, open a documentation issue on . We'll evaluate the issue and update the documentation accordingly. Post a question or a suggestion on the . We'll monitor the posts and, if needed, update the documentation accordingly. Ask questions or provide suggestions in the `#lxc` channel on . Given the dynamic nature of IRC, we cannot guarantee answers or reactions to IRC posts, but we monitor the channel and try to improve our documentation based on the received feedback. % Include content from ```{include} README.md :start-after: <!-- Include start docs --> ``` When you open a pull request, a preview of the documentation output is built automatically. GitHub runs automatic checks on the documentation to verify the spelling, the validity of links, correct formatting of the Markdown files, and the use of inclusive language. You can (and should!) run these tests locally as well with the following commands: Check the spelling: `make doc-spellcheck` Check the validity of links: `make doc-linkcheck` Check the Markdown formatting: `make doc-lint` Check for inclusive language: `make doc-woke` ```{note} We are currently in the process of moving the documentation of configuration options to code comments. At the moment, not all configuration options follow this approach. ``` The documentation of configuration options is extracted from comments in the Go code. Look for comments that start with `gendoc:generate` in the code. When you add or change a configuration option, make sure to include the required documentation comment for it. Then run `make generate-config` to re-generate the `doc/config_options.txt` file. The updated file should be checked in. The documentation includes sections from the `doc/config_options.txt` to display a group of configuration options. For example, to include the core server options: ```` % Include content from ```{include} config_options.txt :start-after: <!-- config group server-core start --> :end-before: <!-- config group server-core end --> ``` ```` If you add a configuration option to an existing group, you don't need to do any updates to the documentation files. The new option will automatically be picked up. You only need to add an include to a documentation file if you are defining a new group.