blue-yonder / pyscaffold

94%

master: 98%

LAST BUILD ON BRANCH fix-version-on-empty-repo

branch: fix-version-on-empty-repo

CHANGE BRANCH

x

Reset

• fix-version-on-empty-repo
• 3.0b2
• assert_setuptools_ver
• bugfix
• bugfix_release
• cookiecutter_fix
• dev
• develop
• django_fix
• drop_pbr
• drop_py2_support
• fix_misleading_error
• include_six
• increase_min_setuptools_ver
• master
• remove-stringio-usage
• requires-io-master
• setuptools_scm
• sphinx_bug
• tox_templates
• update_cfg
• updated_deps
• v0.2
• v0.3
• v0.4
• v0.4.1
• v0.5
• v0.6
• v0.6.1
• v0.7
• v0.8
• v0.9
• v1.0c1
• v1.0c2
• v1.0c3
• v1.1
• v1.1c1
• v1.2
• v1.2c1
• v1.3
• v1.3.1
• v1.3.2
• v1.3c1
• v1.3c2
• v1.4
• v2.0.1
• v2.0.2
• v2.0.3
• v2.0.4
• v2.0b1
• v2.0b2
• v2.0b3
• v2.0b4
• v2.0b5
• v2.1
• v2.1b1
• v2.2
• v2.2.1
• v2.2b1
• v2.2b2
• v2.2b3
• v2.2b4
• v2.2b5
• v2.2b6
• v2.2c1
• v2.2c2
• v2.3
• v2.3c1
• v2.3rc10
• v2.3rc11
• v2.3rc12
• v2.3rc13
• v2.3rc9
• v2.4
• v2.4.1
• v2.4.2
• v2.4.3
• v2.4.4
• v2.4.4rc1
• v2.4rc1
• v2.4rc2
• v2.4rc3
• v2.4rc4
• v2.5.10
• v2.5.10rc1
• v2.5.11
• v2.5.6
• v2.5.6b1
• v2.5.7
• v2.5.7rc1
• v2.5.8
• v2.5.8rc2
• v2.5.8rc3
• v2.5.9
• v2.5a2
• v2.5b1
• v2.5b2
• v2.5b3
• v2.5b4
• v2.x
• v3.0
• v3.0.1
• v3.0.1rc2
• v3.0.2
• v3.0.2rc4
• v3.0.3
• v3.0.x
• v3.0a10
• v3.0a2
• v3.0a4
• v3.0a5
• v3.0a9
• v3.0b1
• v3.0rc1
• v3.0rc2
• v3.0rc3
• v3.0rc4
• v3.0rc5
• v3.0rc6
• v3.1
• v3.1.x
• v3.1b2
• v3.1rc1
• v3.1rc2
• v3.x

Build # 390

Build Type

push

travis-ci

Committed by xhochy

Commit Message

Handle an empty GIT repository for versioning

In the case where a pyscaffold project is moved into a new, yet empty
GIT repository, git describe fails with exit 128 due to not having any
revision, i.e. there is also no HEAD.

As we cannot distinguish `git describe` failing between an empty
repository and being outside of a directory, we also execute
`git show-refs --tags` as this will succeed in a git repository with
commits and exit with exit code 1 if inside a repository with no
commits. (In case of other errors, `git show-refs --tags` will exit with
an exit code no in 0, 1 (mostly 128) so that we can distinguish the
problem here by using the exit code of the command.)

Only in this case handle the error and do the same actions as if an
invalid tag (format) was given.

Run Details

534 of 566 relevant lines covered (94.35%)

0.94 hits per line