adoptium / adoptium/github-release-scripts

Should `TIMESTAMP` be required when publishing nightlies

Open
#93 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
5
Forks
21
Avg merge
6d 7h
Merged PRs (30d)
3

Description

There is a conflict between two parts of the process.
In the refactor release tool job it says `Optional timestamp to add for nightly builds.` against the description of the `TIMESTAMP` field
But if you try to run without a TIMESTAMP set the job says `Nightly must have a TIMESTAMP set`
Is it optional, or is it mandatory? Either way, the messages need to be consistent with each other.

Contributor guide

Open the contributing guide

Research direction

Start by locating the refactor release tool job and the TIMESTAMP validation mentioned in the issue. Compare the field description with the nightly error message and determine the intended requirement; done means the validation and user-facing descriptions consistently reflect whether TIMESTAMP is optional or mandatory.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, shell
Domain
release
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.