Skip to content

Conversation

@arpad-csepi
Copy link
Member

No description provided.

@arpad-csepi arpad-csepi requested a review from a team as a code owner November 17, 2025 08:59
@github-actions
Copy link
Contributor

github-actions bot commented Nov 17, 2025

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed⏩ skipped⏩ skipped✅ passedNov 17, 2025, 5:18 PM

@github-actions github-actions bot added the size/XS Denotes a PR that changes 0-49 lines label Nov 17, 2025
@arpad-csepi arpad-csepi linked an issue Nov 17, 2025 that may be closed by this pull request
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we only make the release actions callable with the workflow_dispatch instead of the whole CI pipeline?

also, this makes the release run on every CI push, so we would be releasing for each PR merge

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed all workflow_dispatch input expect the release one. The if condition for the release is checking the git ref for tag as well (as before), so we will not releasing with each PR.

@arpad-csepi arpad-csepi force-pushed the ci/enable-more-workflow-dispatch branch from dc9ae9b to dc16187 Compare November 17, 2025 17:18
@arpad-csepi
Copy link
Member Author

This PR closes as the solution with workflow_dispatch is no different that much as the current git tag based release CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS Denotes a PR that changes 0-49 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI support for workflow dispatch event type

3 participants