Release process: "does not appear to be a git repository" #24329

issue JeremyRand opened this issue on February 13, 2022
  1. JeremyRand commented at 5:51 AM on February 13, 2022: contributor

    The release-process.md docs erroneously omit the remote name from git fetch.

    Expected behavior

    git fetch should complete without errors.

    Actual behavior

    fatal: 'v22.0' does not appear to be a git repository
    fatal: Could not read from remote repository.
    

    To reproduce

    Follow steps in release-process.md through this line:

    git fetch "v${VERSION}"

    System information

    Bitcoin Core b6b7815ddcff53177bb1f6318b39a4134cf42cb1, self-compiled.

    Whonix 16 inside Qubes 4.1, Intel Haswell, HDD.

    git v2.30.2.

    Replacing the offending line with git fetch origin "v${VERSION}" works fine.

  2. JeremyRand added the label Bug on Feb 13, 2022
  3. JeremyRand referenced this in commit 876b91c383 on Feb 13, 2022
  4. MarcoFalke closed this on Feb 13, 2022

  5. MarcoFalke referenced this in commit b1aa3b1959 on Feb 13, 2022
  6. sh15h4nk referenced this in commit 54d9e47c9e on Feb 13, 2022
  7. rebroad referenced this in commit a6677b6a91 on Feb 15, 2022
  8. hmel referenced this in commit a397799f0a on Feb 20, 2022
  9. DrahtBot locked this on Feb 13, 2023

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-15 03:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me