-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
Which branch should I submit to? #190
Comments
Yes, the current branch management is not standardized. To solve this problem, I suggest creating a release candidate (rc) branch to release the next version lib. All PRs should request be merged into the RC branch. At the same time, the rc branch uses GitHub Actions to run unit test tasks. After release, the rc branch will be merged into the main branch. |
I think this is feasible, so when would be a good time to start? Does anyone have any other suggestions? |
I created the rc branch for release candidate. All PRs should be merged into the rc branch. The main branch will be frozen. |
In contributing-guide, It mentioned to submit to the v2 branch.
But the v2 branch doesn't have GitHub Actions.
Like #145 , PR may fail in test.
The text was updated successfully, but these errors were encountered: