liatrio / liatrio/github-actions
Conventional Release fails when repo has no tags
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 9
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
When setting up a fresh repo and adding the Conventional Release action into a workflow, the pipeline fails with
fatal: No names found, cannot describe anything.
Error: Process completed with exit code 128.
Which isn't the most helpful error message, I believe the issue stems from this step in the entrypoint script https://github.com/liatrio/github-actions/blob/master/conventional-release/entrypoint.sh#L19 where we try to describe the current tags of the repo.
Contributor guide
No contributing guide indexed for this repository
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 conventional-release/entrypoint.sh at line 19, where the action describes repository tags. Reproduce the workflow in a fresh repository with no tags and verify the resulting behavior. Done means the no-tags case no longer produces the unhelpful fatal git error and instead provides an appropriate outcome or message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, shell
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100