After we create the project's repositories, we should config the branch protection rules of every single repositories in order to make everyone follow the constraints. So that it would be easier for everyone when we want to revisit issues.
@thewro11 recommends that we should follow the GitHub conventions -- when an issue is created for modifying source code in repository, a new branch should also be created and tied with that issue. Whenever the branch is merged to development branch, that issue is also marked as closed. This can help us know which issue the branch belongs to, and developer can revert that changes if they find out later that it is unintentional.
Acceptance Criteria:
Config branch protection rules on line-bot-webhook-frontend repository.
Config branch protection rules on web-frontend repository.
Config branch protection rules on api-backend repository.
Ensure that branch protection rules are similar to each repositories.
After we create the project's repositories, we should config the branch protection rules of every single repositories in order to make everyone follow the constraints. So that it would be easier for everyone when we want to revisit issues.
@thewro11 recommends that we should follow the GitHub conventions -- when an issue is created for modifying source code in repository, a new branch should also be created and tied with that issue. Whenever the branch is merged to development branch, that issue is also marked as closed. This can help us know which issue the branch belongs to, and developer can revert that changes if they find out later that it is unintentional.
Acceptance Criteria: