ci: Move CI related files into own directory

.github/workflows/main.yml

@@ -23,8 +23,8 @@ jobs:
       - uses: actions/checkout@v2
       - name: Run tests
         run: |
-          docker build -f Dockerfile.${{ matrix.flavor }} -t profanity .
-          docker run profanity ./ci-build.sh
+          docker build -f ci/Dockerfile.${{ matrix.flavor }} -t profanity .
+          docker run profanity ./ci/ci-build.sh
 
   linux-meson:
     runs-on: ubuntu-latest
@@ -40,8 +40,8 @@ jobs:
         env:
           OMEMO_BACKEND: libomemo-c
         run: |
-          docker build -f Dockerfile.${{ matrix.flavor }} -t profanity .
-          docker run -e OMEMO_BACKEND profanity ./ci-meson-build.sh
+          docker build -f ci/Dockerfile.${{ matrix.flavor }} -t profanity .
+          docker run -e OMEMO_BACKEND profanity ./ci/ci-meson-build.sh
 
   code-style:
     runs-on: ubuntu-22.04

CONTRIBUTING.md

@@ -48,7 +48,7 @@ meson setup build_run -Domemo=enabled -Domemo-backend=libomemo-c
 3. Run: `./build_run/profanity`
 
 We also have a [build section](https://profanity-im.github.io/guide/latest/build.html) in our user guide.
-You might also take a look at the `Dockerfile.*` in the root directory.
+You might also take a look at the `Dockerfile.*` in the `ci` directory.
 
 ## Submitting patches
 We recommend for people to always work on a dedicated git branch for each fix or feature.
@@ -180,7 +180,7 @@ snippet to `.git/hooks/pre-push`:
 ```shell
 #!/bin/sh
 set -e
-./ci-build.sh
+./ci/ci-build.sh
 ```
 
 This will run the same tests that the CI runs and refuse the push if it fails.
@@ -202,7 +202,7 @@ In cases where you want to disable automatic formatting for a specific block of
 ## Verification & Testing
 
 ### Running unit tests
-Run `make check` to run the unit tests with your current configuration or `./ci-build.sh` to check with different switches passed to configure.
+Run `make check` to run the unit tests with your current configuration or `./ci/ci-build.sh` to check with different switches passed to configure.
 
 ### Writing unit tests
 We use the [cmocka](https://cmocka.org/) testing framework for unit tests.