Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Conventional Release fails when repo has no tags

Open
  • Is something wrong?
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

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.

Dominant language
Shell
Stars
9
Forks
16
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.