duke-git / lancet

A comprehensive, efficient, and reusable util function library of Go.

Home Page:https://www.golancet.cn/en/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Which branch should I submit to?

cannian1 opened this issue · comments

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.

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.

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 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.