- develop/{issue_number}: for blog maintenance
- docs/{issue_number}: for markdown relatives
- gh-pages: for deployment
- SEMANTIC COMMITS that @Queue-ri told you.
- All commit messages should contain issue numbers.
Before you deploy, you must check if:
- all edits are merged into mainbranch
- you're currently on mainbranch
- the deployment commit message contains the lastest SHA of mainbranch
then launch:
npm run deploy -- -m "chore: Deploy {latest_main_sha}"
