Making CI for testing generated proto correctness

.github/workflows/check-generated.yml

@@ -0,0 +1,29 @@
+# Verify that generated code is up-to-date.
+#
+# Note that we run these checks regardless whether the input files have
+# changed, because generated code can change in response to toolchain updates
+# even if no files in the repository are modified.
+name: Check generated code
+on:
+  workflow_dispatch:
+  pull_request:
+    branches:
+      - '*'
+
+permissions:
+  contents: read
+
+jobs:
+  check-proto:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/setup-go@v3
+        with:
+          go-version: '1.18'
+
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 1  # we need a .git directory to run git diff
+
+      - name: "Check protobuf generated code"
+        run: contrib/scripts/check-generated.sh

chain.schema.json

@@ -9,4 +9,4 @@
       "linux/arm64": "https://github.com/osmosis-labs/osmosis/releases/download/v10.0.0/osmosis-10.0.0-linux-arm64"
     }
   }
-}
+}

contrib/scripts/check-generated.sh

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+
+set -euo pipefail
+# Install buf and gogo tools, so that differences that arise from
+# toolchain differences are also caught.
+readonly tools="$(mktemp -d)"
+
+make proto-gen
+
+#Specificially ignore all differences in go.mod / go.sum.
+if ! git diff --stat --exit-code . ':(exclude)*.mod' ':(exclude)*.sum'; then
+    echo ">> ERROR:"
+    echo ">>"
+    echo ">> Protobuf generated code requires update (either tools or .proto files may have changed)."
+    echo ">> Ensure your tools are up-to-date, re-run 'make proto-all' and update this PR."
+    echo ">>"
+    exit 1
+fi