Skip to content

Add LSP code lenses for buf generate and checking for plugin updates#4480

Open
stefanvanburen wants to merge 2 commits intomainfrom
svanburen/buf-gen-yaml-code-actions
Open

Add LSP code lenses for buf generate and checking for plugin updates#4480
stefanvanburen wants to merge 2 commits intomainfrom
svanburen/buf-gen-yaml-code-actions

Conversation

@stefanvanburen
Copy link
Copy Markdown
Member

Similar to #4438. Checking for plugin updates makes sense to me; perhaps buf generate is a step too far, but we've largely designed buf.gen.yaml v2 to be self contained (except the occasional need for multiple with --template), so adding the possibility to run buf generate seems reasonable to me.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 17, 2026

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedApr 17, 2026, 7:18 PM

@stefanvanburen
Copy link
Copy Markdown
Member Author

Upgrade diagnostics in neovim:

image

Running generate on the test file (it's busted, so it comes back as an LSP notification):

image

@stefanvanburen stefanvanburen marked this pull request as ready for review April 17, 2026 19:03
Similar to #4438. Checking for plugin updates makes sense to me; perhaps
`buf generate` is a step too far, but we've largely designed
`buf.gen.yaml` v2 to be self contained (except the occasional need for
multiple with `--template`), so adding the _possibility_ to run `buf
generate` seems reasonable to me.
@stefanvanburen stefanvanburen force-pushed the svanburen/buf-gen-yaml-code-actions branch from 82cdac3 to 7706a76 Compare April 17, 2026 19:04
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