You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I am experiencing this problem as well - This seems to be happening because of the renaming of master to main which all new repos will have by default.
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 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
main
as a default branch instead ofmaster
.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
.The text was updated successfully, but these errors were encountered: