In preparation for the upcoming Github feature described in github/roadmap#63 I renamed the base branch of my new repo to main instead of the default master.
Bundlewatch reported the following failure on that repo.
$ bundlewatch
[INFO] Retrieving comparison
[ERROR] Unable to fetch fileDetails for baseBranch=master from https://service.bundlewatch.io/store code=Request failed with status code 404
[INFO] master !== main, no results saved
[INFO] Saving results
The error can also be seen live on CI: https://travis-ci.com/github/nilfalse/ctf/jobs/370145494
Steps to reproduce
- Setup Github repo to have
main as a default branch instead of master.
- Delete
master branch.
What is the expected behavior?
Bundlewatch should be able to compare size to any default branch in the Github repo even if it's not called master.
In preparation for the upcoming Github feature described in github/roadmap#63 I renamed the base branch of my new repo to
maininstead of the defaultmaster.Bundlewatch reported the following failure on that repo.
The error can also be seen live on CI: https://travis-ci.com/github/nilfalse/ctf/jobs/370145494
Steps to reproduce
mainas a default branch instead ofmaster.masterbranch.What is the expected behavior?
Bundlewatch should be able to compare size to any default branch in the Github repo even if it's not called
master.