set branch protect rule

[junbeomlee]

No description provided.

[queuestack]

How about using master, develop, feature, hotfix branch?
master : branch for release
develop : integration branch for features
feature : branch for each feature, ex. feature/new-feature
hotfix: branch for fixing bug, ex hotfix/some-bug

Btw, some articles like gitflow suggests 'release' branch is needed.
I think our project can be covered without release branch.

[kwongiho]

@queuestack
I think we need 'release branch' for deploy and scheduling.
We can easily schedule the deployment with Milestone If we use the 'release branch'.
If not, we will have to set the exact rules for when to deploy it
Do you have any idea about this ?

[zeroFruit]

I think both ideas are good. so how about make both branches?

[queuestack]

@kwongiho @zeroFruit
I agree with KwonGiho's opinion.
'release branch' will helps us to schedule the deployment.
It will be a good idea to use five branches in our project.

[queuestack]

Our bnach rules are set like below.

master : branch for release
release : branch for release.
develop : integration branch for features
feature : branch for each feature, ex. feature/new-feature
hotfix: branch for fixing bug, ex hotfix/some-bug

This issue should be closed after adding branch guide line to CONTRIBUTING.md

[kwongiho]

I finished setting up the protect rule for master and develop branch.
We have to get one more approve before merge