Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes a somewhat mysterious bug that has been causing CI builds to fail. This PR:
Why are we doing this?
We need a working CI process to catch bugs and linting issues before merging to production. I opened a PR with very minor changes the other day and immediately discovered our CI github action was failing. My PR only affected our readme. The error appeared unrelated to my changes and was occurring early, just as Pipenv attempted to install packages:
I tried a number of things to solve this issue and the best I could determine is that there was some kind of dependency issue in our
Pipfile
orpipfile.lock
. I kept hitting errors whenever I tried to rebuild the lock file from the existing Pipfile.Pinning dependencies and the Python version seems to have fixed things.
Are there any smells or added technical debt to note?