Skip to content
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

Add flag --only-changes to filter commits for modules and plugins #3560

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

emcfarlane
Copy link
Contributor

This adds a flag --only-changes to the commands buf registry {module,plugin} commit list to filter out any commits without a changed digest. By default all commits are listed. This is similar to the UI view "Hide commits with no changes" in the BSR.

This adds a flag `--only-changes` to the commands `buf registry {module,plugin}
commit list` to filter out any commits without a changed digest. By
default all commits are listed. This is similar to the UI view "Hide
commits with no changes" in the BSR.
@emcfarlane emcfarlane requested a review from doriable December 20, 2024 14:42
Copy link
Contributor

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedDec 20, 2024, 2:43 PM

@bufdev
Copy link
Member

bufdev commented Dec 20, 2024

Need to workshop naming here live. The "no changes" labeling always bothered me a tad, so we can hammer out both at once on Tuesday! Prob will be a 5-10 minute call.

@mfridman
Copy link
Member

More of a driveby to suggest some names: --content-only, --filter-content-only or --source-only.

Maybe just me, but I've always thought about this behavior as "metadata" (vcs url, deps) vs "content" (proto, license, etc.) changes.

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.

3 participants