How to deploy changes to production
[!CRITICAL] BRANCHING RULES
mainis PRODUCTION. Be extremely careful before pushing tomain.devis for DEVELOPMENT.- Ensure you are on the correct branch before taking any action.
// turbo
npm run test:run
[!WARNING] If tests fail:
- Check if main code has a bug - fix the code first
// turbo
npm run lint
[!NOTE] Ensure all linting errors are resolved.
Run the Salesforce Code Analyzer to check for security and quality issues.
sf scanner:run --target . --category Security,Performance,BestPractices
[!IMPORTANT] Ethical Compliance
- Fix, don't trick. Address the root cause of any violations.
- Do not manipulate code or configuration solely to bypass checks without fixing the underlying issue.
- Ensure the codebase remains secure and performant.
// turbo
npm run typecheck
npm run build
[!CAUTION] Always ask the user before committing.
git add . && git commit --author="Gaurav Singla <[email protected]>" -m "<type>: <description>" && git push origin main
| Type | Description |
|---|---|
feat: | New feature |
fix: | Bug fix |
refactor: | Code refactoring |
style: | UI/styling changes |
docs: | Documentation |
test: | Test changes |
chore: | Maintenance |
git add . && git commit --author="Gaurav Singla <[email protected]>" -m "feat: add persistent Google OAuth with refresh tokens" && git push origin main
main triggers automatic deployment on Vercel