-
Notifications
You must be signed in to change notification settings - Fork 772
Refactor buf modules #4083
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Refactor buf modules #4083
Conversation
@@ -131,7 +131,7 @@ jobs: | |||
- uses: actions/checkout@v4 | |||
- uses: bufbuild/buf-action@dfda68eacb65895184c76b9ae522b977636a2c47 #v1.1.4 | |||
with: | |||
input: "proto" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upon making changes to our CI I think there was a miss and we need another github action to run the linter on the connect module as a follow-up to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue: #4084
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to not use a github action for a new linter? Ideally this one should go away in favor of a task that can be executed both locally and in CI.
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
Coreth branch: ava-labs/coreth#1047 |
Why this should be merged
We compile our buf modules seprately since the
proto
module doesn't want to compile stuff with theconnect
plugin. This PR puts our buf modules under a common directory instead of separateproto
andconnectproto
directories.How this works
Moves files
How this was tested
CI
Need to be documented in RELEASES.md?
No