bndr / pipreqs

71%

LAST BUILD ON BRANCH master

branch: master

CHANGE BRANCH

x

Reset

• master
• drop_python2
• next
• pypy
• v0.1.9
• v0.2.1
• v0.2.2
• v0.2.4
• v0.2.5
• v0.2.7
• v0.2.8
• v0.2.9
• v0.3.0
• v0.3.1
• v0.3.2
• v0.3.8
• v0.4.0
• v0.4.1
• v0.4.10
• v0.4.2
• v0.4.4
• v0.4.5
• v0.4.6
• v0.4.7
• v0.4.8

Build # 316

Build Type

push

travis-ci

Committed by alan-barzilay

Commit Message

Revert all commits since last release

By reverting all commits done since release v0.4.10 we will have the
master branch synchronized with the latest release available in pipy.

All commits done since the latest release will be moved to another
branch called `next` where we will centralize development. Once we are ready
for a new release of pipreqs, the `next` branch will be merged back on to
master and a new release will be made.

This change will make development more organized and will avoid new
issues from users complaining about features only present in master not working
on their installation of pipreqs.

I would also like to thank @pedroteosousa for his help on reverting and
squashing all commits

Run Details

177 of 248 relevant lines covered (71.37%)

2.8 hits per line