check generated code on CI (#16)

Dogacel · Oct 13, 2023 · 1eb7cb2 · 1eb7cb2
1 parent 19aab38
commit 1eb7cb2
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 0 deletions.
diff --git a/.DS_Store b/.DS_Store
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
@@ -18,6 +18,11 @@ jobs:
         with:
           arguments: build koverXmlReport --scan
 
+      - name: Check auto-generated files are committed
+        shell: bash
+        run: |
+          git diff --exit-code
+
       - name: Upload coverage reports to Codecov
         uses: codecov/codecov-action@v3
         env:

diff --git a/.gitignore b/.gitignore
@@ -5,3 +5,5 @@
 build
 
 .idea
+
+.DS_Store
diff --git a/README.md b/README.md
@@ -76,6 +76,8 @@ tests.
     - This is a separate subproject makes sure we are not breaking the compilation of our main app when the
       generated code is not compiling after making some changes.
     - We store the generated code in version control showcase and review the generated code.
+    - Make sure you run `./gradlew build` after you modify the code to generate the newest files. If newest files are
+      not committed, the CI check will fail.
 
 Linting can be done via