* use buf ci
* check breakage against target branch
* test proto
* fix repo
* setinput
* undo proto change
* minor change
* test without subdir
* addback subdir
* try without input
* proto change
* fix ci
* remove head
* add proto
* add back
* add .git
* test
* test++
* test+++
* something
* something
* something++
* test
* test
* do different design
* revert proto change
* docs
* revert comment
* Update tooling around docker
* Run commands
* Remove swagger gen for now
* Update proto-gen-any
* Fix indentn
* Use CURDIR
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Try reduce the overall build time by splitting test coverage
across 4 instances.
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com>
* test paths directive
* change proto files
* test paths on code coverage
* have parts of ci only run when go files are touched
* add readme badge
* bring back green checks
* remove paths
* green check linting
* add tests no run
Cancel ci if no .go files have been touched. There is no clean way of
doing this so i opted to `exit 1` on the diff job if no go files were
changed and have builds depend on diff passing
- migrate proto checks to github actions.
- providing make commands to use buf within docker.
- test-sim-multi-seed-long migration to github actions. Follows same
logic and only runs on release branches.
- add protobuf section to CONTRIBUTING.md.
