docs: Add a section about Conventional Commit (#1318)

Add a section about Conventional Commit in dev doc

---------

Co-authored-by: Alice Rühl <[email protected]>

docs/development/SETUP.md

@@ -1,7 +1,9 @@
 # Installation and Usage
-The steps below will walk you through setting up your own instance of the project. 
+
+The steps below will walk you through setting up your own instance of the project.
 
 ## Install Project Dependencies
+
 To set up the development environment for this website, you'll need to install the following on your system:
 
 - [Node](http://nodejs.org/) v20 (To manage multiple node versions we recommend [nvm](https://github.com/creationix/nvm))
@@ -20,16 +22,19 @@ Install Node modules:
 ```
 yarn install
 ```
-This command  will install all the dependencies and devtools needed for local development. 
+
+This command will install all the dependencies and devtools needed for local development.
 
 ## Usage
 
 ### Config files
+
 Configuration is done using [dot.env](https://parceljs.org/features/node-emulation/#.env-files) files.
 
 These files are used to simplify the configuration of the app and should not contain sensitive information.
 
 Copy the `.env.local-sample` to `.env.local` to add your configuration variables.
+
 ```sh
 cp .env.local-sample .env.local
 ```
@@ -43,6 +48,7 @@ Get your Mapbox access token from Mapbox Dashboard. Put the key in `.env.local`
 ```
 yarn serve
 ```
+
 Compiles the sass files, javascript, and launches the server making the site available at `http://localhost:9000/`
 The system will watch files and execute tasks whenever one of them changes.
 The site will automatically refresh since it is bundled with livereload.
@@ -57,41 +63,62 @@ The site will automatically refresh since it is bundled with livereload.
 ### Lint & TS-Check
 
 #### GitHub Action
+
 VEDA-UI includes a GitHub action for checking TypeScript and lint errors. If your changes trigger any of these errors, your pull request (PR) will be marked as 'Some checks were not successful.'
 
 #### Pre-commit Hook
+
 Additionally, there's a pre-commit hook that performs the same error checks. This helps developers identify and address issues at an earlier stage. If you need to bypass the check (to make a local temporary commit etc.), include the `--no-verify`` flag in your commit command.
 
+### Conventional Commit
+
+The title of any PR to `main` should follow [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/). This is to make sure the automatic versioning and release works seamlessly. Please give it a read to [its summary](https://www.conventionalcommits.org/en/v1.0.0/#summary) before making a PR.
+
+An example PR title could look like this:
+
+- `feat: Implement new component`: This commit will bump the minor version.
+- `fix: typo in description`: This commit will bump the patch version.
+- `feat!: New component that is not compatible`: `!` is a shortcut for `BREAKING CHANGE`. This commit will bump the major version.
+
+We currently support the following task types. Any type other than `feat` will be treated as a patch version change (unless it is a breaking change):
+`["feat","fix", "docs", "test", "ci", "refactor", "chore", "revert"]'`
+
 ### Testing
 
 ## Unit tests
 
 `yarn test`
 
 ## End-to-end tests
+
 Make sure the development server is running (`yarn serve`)
 
 `yarn test:e2e --ui`
 
-Alternatively, you can install the playwright extension for vs code (ms-playwright.playwright) and run the tests directly from there. It allows to run the tests in watch mode, open the browser or trace viewer, set breakpoints,... 
+Alternatively, you can install the playwright extension for vs code (ms-playwright.playwright) and run the tests directly from there. It allows to run the tests in watch mode, open the browser or trace viewer, set breakpoints,...
 Again, make sure that the development server is running (`yarn serve`).
 
 ## Deployment
+
 To prepare the app for deployment run:
 
 ```
 yarn build
 ```
+
 or
+
 ```
 yarn stage
 ```
+
 This will package the app and place all the contents in the `dist` directory.
 The app can then be run by any web server.
 
 **When building the site for deployment provide the base url trough the `PUBLIC_URL` environment variable. Omit the trailing slash. (E.g. https://example.com)**
 
 If you want to use any other parcel feature it is also possible. Example:
+
 ```
 PARCEL_BUNDLE_ANALYZER=true yarn parcel build app/index.html
 ```