opensearch-project / opensearch-project/sql-jdbc
[BUG] Release workflow is missing 2PR approval process
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Adding this issue as bug because the current 1-click process in this repository lacks this feature. See details here https://github.com/opensearch-project/opensearch-build/issues/3111
Sample PR: https://github.com/opensearch-project/opensearch-java/pull/383
To Reproduce
Push a tag to this repo and release is drafted immediately. It should ask for approval before moving forward
Expected behavior
The release-drafter workflow should be blocked asking for approval from 2 maintainers/codewoners to approve the release.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the release-drafter workflow and compare its tag-triggered path with the approval behavior described in the linked opensearch-build issue and sample PR. Done means a tag no longer advances the release immediately and the workflow requests approval from two maintainers or code owners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100