Commits start with a type: feat (new feature), fix (bug fix), docs (documentation), refactor (code restructuring), test (tests), chore (maintenance). Followed by a concise description in present tense. Example: 'feat: add connection request API'.
Use main (production), develop (integration), feature/* (new features), bugfix/* (fixes), and hotfix/* (urgent production fixes). Create feature branches from develop, merge back to develop, and merge develop to main for releases.
node_modules/, .env files, logs (*.log, logs/), build artifacts (dist/, build/), IDE files (.vscode/, .idea/), OS files (.DS_Store), and coverage reports (coverage/). Never commit secrets or dependencies.
Create a .github/workflows/ci.yml file that runs on push and PR to main/develop. Steps: checkout code, setup Node.js, npm install, npm run lint, npm test. This ensures all code is tested before merging.
Browse all our FAQs or reach out to our support team
Your learning library
Find your next course. Build something great.
