Manual trigger Github CI workflow with config options [DBZ-6333]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-6333](https://issues.redhat.com/browse/DBZ-6333)
This issue is triggered by https://github.com/debezium/debezium/pull/4449#discussion_r1164198771
In general I'd prefer to have a generic workflow that will be triggered only manually and applied to the whole repository. As part of the workflow start it would be possibly to pass arbitrary Maven CLI options to limit which project to run on and which test to execut.
Contributor guide
Research direction
Start by reviewing the linked discussion in pull request #4449 and the migrated DBZ-6333 issue, then inspect the repository's existing GitHub Actions workflows. The issue names no file or test; completion would mean a manually triggered repository-wide workflow accepts Maven CLI options that limit the project and test to execute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100