Update contributing guide

Author: medihack

CONTRIBUTING.md

@@ -24,10 +24,28 @@ It also contains a Django example project to play around with the features.
 git clone https://github.com/openradx/adit-radis-shared.git
 cd adit-radis-shared
 uv sync
-uv run ./cli.py compose-up
+cp ./example.env ./.env  # adjust the environment variables to your needs
+uv run ./cli.py compose-watch
 ```
 
 The development server of the example project will be started on <http://localhost:8000>
 
-If a library dependency is changed, the containers need to be rebuilt (e.g. by running
-`uv run ./cli.py compose-down && uv run ./cli.py compose-up`).
+File changes will be automatically detected and the servers will be restarted. When library
+dependencies are changed, the containers will automatically be rebuilt and restarted.
+
+## Reporting Issues
+
+If you encounter bugs or have feature requests, please open an issue on GitHub. Include as much detail as possible, including steps to reproduce the issue.
+
+## Making Changes
+
+1. Fork the repository and create a new branch for your feature or bug fix.
+2. Make your changes and ensure that they adhere to the Google Python Style Guide.
+3. Write tests for your changes and ensure that all tests pass.
+4. Commit your changes to a new branch with a clear and descriptive commit message.
+5. Push your changes to your forked repository and create a pull request against the main repository.
+6. Ensure that your pull request is linked to an issue in the main repository.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the AGPL-3.0 license.