fregante/daily-version-action

Avoid releasing too often / too little

Open

#17 opened on Jan 17, 2021

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (5 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (22 stars)
PR merge metrics
 (PR metrics pending)

Description

There's no need to have a release for just one commit (for example if there's a cronjob running the day after a manual release).

  • A maxCommit option (currently: 1) would define how many commits are needed for a new release.
  • A maxAge option (currently: 0) would define how many days a commit can wait to be released.

These 2 options complement each other. For example, "don't release 2 commits unless they've already been pushed 5 days ago"

However I think that there should be a way to skip this logic. Maybe manual releases can automatically be detected.

Contributor guide

Research direction
Examine the current release logic in daily version action to understand how to add maxCommit and maxAge options. Look for existing tests or similar actions for inspiration.
Tech stack
javascriptnodejsgithub actions
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScriptGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60