bazel-contrib / bazel-contrib/.github

prerelease should be set automatically

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
good first issue help wanted
Dominant language
No language data
Stars
7
Forks
18
PR merge metrics
No merged PRs in 30d

Description

Currently, the prerelease needs to be set manually in the release workflow which makes it brittle to mistakes. We should set the prerelease to true based on semantic versioning and introduce a new option to opt-in to this behavior.

Contributor guide

Open the contributing guide

Research direction

Start by reading the repository's release workflow and identify where prerelease is currently set manually. Check how semantic versioning is represented there, then define the opt-in option and verify that prerelease becomes true for prerelease versions while existing behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.