### Rationale First of all, thanks for this awesome project :smile: I'm working with a team that has a hook repository, in which each commit on the main branch is considered stable meaning they avoid tagging any commits. To update this hook repo, I thought I could use the --bleeding-edge flag to just fetch the newest commit hash, but unfortunately, it doesn't work. When trying to update with the flags `-v` and `--bleeding-edge repo`, I get the following warnings ``` ⚠ repo - --all-versions option ignored (--bleeding-edge) ⚠ repo - 0 tags/hashes fetched ``` I expect it to find the latest git hash and use that. Is this something you could support / fix? #### Possible cause After investigating the code, I found that it does correctly find the latest hash ``` get_git_remote_latest_hash("repo-link") 'dbdXXXXX7cc1aXXXXXXXXXXXXXXXXXXXXXXXXXXX' ``` but it (obviously) cannot find any version-tags. ``` get_git_remote_tags_list("repo-link") git.exc.GitCommandError: Cmd('git') failed due to: exit code(2) cmdline: git ls-remote --sort=v:refname --exit-code --tags repo-link ``` Since `.result()` is called on this failed tag-retrieval-task (in https://gitlab.com/vojko.pribudic.foss/pre-commit-update/-/blob/main/src/pre_commit_update/managers/repo.py#L101), an error is raised and `None, None` is returned, even though the first element of the tuple could be the already retrieved, latest commit hash. ### Type (select one) - [ ] Bug - [x] Feature request - [ ] Suggestion ### Pre-submit criteria - [x] No similar issue/feature request/suggestion exists - [x] Correct labels have been set for this issue/feature request/suggestion - Not sure how :/