Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pyup not taking the default set branch in Github
See original GitHub issuePrivate repository (private access enabled obviously). I pushed a new branch ‘develop’ to my repository and changed it to be the default. I closed a pull request and deleted the branch, however the new PR was still against the old ‘master’ branch (which is no longer default and has been set to be a protected branch). I have tried removing the repository from pyup.io and re-adding it and I still got the same behavior.
I had to add a .pyup.yml file with branch = develop to get the correct behavior but the docs state that pyup makes PR’s against the default branch on the repository (usually master)
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello,
FYI, this also occurs with public repositories.
similar problem here, I had to create a master branch with only the .pyup.yml file.