We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
0.11
next
master
current
We're changing the names of the branches to better represent what they're supposed to refer to, as well as to accomodate some structural changes:
If you're directly referring to these branches in your project, we recommend you switch to the new names so as to prevent issues later on.
The text was updated successfully, but these errors were encountered:
This has been done. :-)
Sorry, something went wrong.
Also, branch protection rules have been expanded to cover all branches, which are currently just current and next.
No branches or pull requests
We're changing the names of the branches to better represent what they're supposed to refer to, as well as to accomodate some structural changes:
current
(Previouslymaster
) will be used for the latest version of the last major release,next
(Previously0.11
) will be used for the next major release in-the-works.If you're directly referring to these branches in your project, we recommend you switch to the new names so as to prevent issues later on.
The text was updated successfully, but these errors were encountered: