Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config file for pyup.io #145

Merged
merged 3 commits into from
May 17, 2018
Merged

Config file for pyup.io #145

merged 3 commits into from
May 17, 2018

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented May 15, 2018

pyup automatically created this PR. It has been modified to reference Pipfile and Pipfile.lock since we have moved to pipenv.

@coveralls
Copy link

coveralls commented May 15, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 41e5010 on pyup-config into 5777856 on development.

@cabarnes
Copy link
Member

Experimental support for pipenv: pyupio/pyup#197

Copy link
Contributor

@ductape ductape left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the file was manually modified to add the pipenv, should the comment from pyup about being auto generated be removed? Or add a note that it is manually managed now?

@cabarnes cabarnes merged commit f853197 into development May 17, 2018
@cabarnes cabarnes deleted the pyup-config branch May 17, 2018 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants