-
Notifications
You must be signed in to change notification settings - Fork 913
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
Change default branch to develop #1013
Comments
The problem with that (at least the last time we looked into it, which was awhile ago) was that If we can resolve that, then absolutely! |
I am not sure if that is really an issue, people should absolutely be pulling at specific tags e.g.
or even
never...
|
@onedr0p Agreed. As well, I hadn't been following the deprecation of go get to install binaries. I'd say once we upgrade to Go v1.17 (which will be in the next release), we should give this a try. |
Closing in favor of #1238 |
@ajvb would it make sense to set the default branch in the Github project settings to the
develop
branch? This would lead to less confusion on new PRs which want to be merged into themaster
branch by default. This would also lead to less confusion on the state of commits, as the develop branch is much more active.The text was updated successfully, but these errors were encountered: