Repository navigation
ci: enable manual workflow dispatch - #254
Merged
Merged
Conversation
This was referenced Nov 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workflow_dispatchto the default-branch CI workflow.enable_destructive_solrcloud_testsboolean input (defaultfalse) so maintainers can select a feature branch and explicitly opt in to destructive SolrCloud checks.Why
GitHub only exposes the Run workflow control when the workflow file supports
workflow_dispatchon the repository's default branch. The existing feature branch already contains the opt-in SolrCloud workflow logic, but the default-branch workflow did not expose manual dispatch.Safety
The destructive test input defaults to
false; normal push and pull-request triggers are unchanged.