Skip to content
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

Renaming the 0.11 branch to next and master to current #216

Closed
aleokdev opened this issue Apr 25, 2022 · 2 comments
Closed

Renaming the 0.11 branch to next and master to current #216

aleokdev opened this issue Apr 25, 2022 · 2 comments

Comments

@aleokdev
Copy link
Contributor

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 (Previously master) will be used for the latest version of the last major release,
  • And next (Previously 0.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.

@aleokdev aleokdev pinned this issue Apr 25, 2022
@bjorn
Copy link
Member

bjorn commented Apr 25, 2022

This has been done. :-)

@bjorn bjorn closed this as completed Apr 25, 2022
@bjorn
Copy link
Member

bjorn commented Apr 25, 2022

Also, branch protection rules have been expanded to cover all branches, which are currently just current and next.

@aleokdev aleokdev unpinned this issue Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants