René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Running 'make test' dies due to no .git when building from a .tar.gz","articleBody":"If you [follow these build instructions](https://github.com/github/git-sizer/blob/master/docs/BUILDING.md#build-using-make) and run `make test` on one of the `.tar.gz` releases you get:\r\n\r\n```\r\n$ make test; echo $?\r\n[...]\r\n        Messages:       command failed; output: \"error: couldn't open Git repository: git rev-parse failed: fatal: not a git repository (or any of the parent directories): .git\\n\\n\"\r\n[...]\r\nmake: *** [gotest] Error 1\r\n2\r\n```\r\n\r\nJust running `git init` in the build directory works around it, but I don't know how much this breaks the tests, if at all:\r\n\r\n```\r\n$ make test; echo $?\r\n[...]\r\nok      github.com/github/git-sizer     0.123s\r\nok      github.com/github/git-sizer/counts      (cached)\r\n?       github.com/github/git-sizer/git [no test files]\r\n?       github.com/github/git-sizer/isatty      [no test files]\r\n?       github.com/github/git-sizer/meter       [no test files]\r\n?       github.com/github/git-sizer/sizes       [no test files]\r\n0\r\n```\r\n\r\nSo now I do `git init` in my packaging script, but it would be neat if this worked out of the box.","author":{"url":"https://github.com/avar","@type":"Person","name":"avar"},"datePublished":"2018-11-16T09:31:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/51/git-sizer/issues/51"}