-
Notifications
You must be signed in to change notification settings - Fork 229
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
Default branch should be "main" not "master" #68
Comments
Why not use |
It's strange when I see my workflow failed due to this reason. |
@counter2015 , there is no release yet and there is no updates of already released version. Use latest version. |
@ad-m I'm not sure, you mean that this issue is fixed in master version? I didn't specify version, and the
I fixed it by following steps
|
PR #69 switch default branch to The simplest solution is use explicit branch ( |
This thing broke my build and I got a lot of mails from GitHub. PR #75 did not fix it for me as I still got mails from GitHub. Part of the stack trace:
This may be caused by the repository being private. Fixed by specifying the branch explicitly using |
The
The request (
Using the public GitHub instance (no EE/On-Prem), but a private repository. |
I believe authorization issue is solved in commit 057a6ba . No longer |
Due to the latest changes to Github, the default branches are now called "main" and not "master". Therefore, the default branch should be "main".
The text was updated successfully, but these errors were encountered: