Skip to content

fix: buf issues#144

Merged
xBlaz3kx merged 5 commits into
v2from
fix/buf-lint
Jun 16, 2025
Merged

fix: buf issues#144
xBlaz3kx merged 5 commits into
v2from
fix/buf-lint

Conversation

@xBlaz3kx

Copy link
Copy Markdown
Collaborator

Proposed changes

  • Fix buf linter issues

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...

@github-actions

github-actions Bot commented Jun 16, 2025

Copy link
Copy Markdown

The latest Buf updates on your PR. Results from workflow Lint / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed❌ failed (1)❌ failed (7)Jun 16, 2025, 9:49 PM

@xBlaz3kx xBlaz3kx merged commit 2bd7661 into v2 Jun 16, 2025
5 of 10 checks passed
@xBlaz3kx xBlaz3kx deleted the fix/buf-lint branch June 16, 2025 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant