eclipse-score / eclipse-score/cicd-workflows
Create a Release Work Flow
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 17
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 17
Description
### What
It seems that there are multiple ways of doing a release, and it would be nice to have a reusable workflow to use for all repos.
There are some repos that have this already but having it central would be good.
**Note that different repos have very different release workflows**
e.g. https://github.com/eclipse-score/baselibs/blob/main/.github/workflows/release.yml
Note: bazel_registry does not need to be considered at this step. it will pull github releases.
### Acceptance Criteria (DoD)
- Release workflow that creates a draft release
### How
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing reusable workflows in eclipse-score/cicd-workflows and compare them with baselibs/.github/workflows/release.yml. Focus on how repository differences are handled, then verify the result against the acceptance criterion: a reusable workflow that creates a draft GitHub release, without adding bazel_registry support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100