-
Notifications
You must be signed in to change notification settings - Fork 31
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
Unclear for contributors which branch to contribute to #141
Comments
Good question.
|
Sorry for the brief issue description and thanks for the elaborate response! I agree that usually the default branch is appropriate to make PR's towards :) I guess this morning specifically I was a bit confused given that the release-1.3.0 and the dev branch were out of sync, while 1.3.0 was already released. I think your proposal under 3 makes sense! For contributors not familiar with the project merging to No strong preference from my side, feel free to close this issue! |
Keeping this issue open, for now. We will revisit |
This repo's default branch is now switched to |
There is both a dev, master and a release-1.3.0 branch.
master
seems outdated,dev
is the default, butrelease-1.3.0
has some changes that are not ondev
.The text was updated successfully, but these errors were encountered: