admin/.github/BRANCH_PROTECTION.md
alisaza f9a9afc697 feat: add layout components for various admin dashboard pages
- Introduced layout components for multiple admin dashboard sections including events, audit logs, bank accounts, blog articles, bookings, chat oversight, cities, contact messages, dashboard, discount codes, event categories, guest lists, identity verifications, manage events, manual notifications, notification rules, payments, provinces, push deliveries, reviews, settlements, sms messages, support tickets, user reports, and users.
- Updated metadata for the auth layout to include the admin page title.
- Modified branch protection documentation to clarify deployment notifications.
2026-09-05 14:29:43 +03:30

1.3 KiB

Branch protection on main (GitHub Pro required)

Private repositories on GitHub Free cannot enable branch protection via API or Settings. Upgrade to GitHub Pro (or make the repo public), then configure:

Settings → Branches → Add branch protection rule → Branch name: main

Recommended settings:

  • Require a pull request before merging
  • Require approvals (optional for solo work)
  • Require status checks to pass before merging
  • Require branches to be up to date before merging

Required status checks — ghabilee-frontend2

  • Dependency vulnerability scan
  • Secret scan
  • Build, test, and quality checks

Until Pro is enabled, use Pull Request → merge (not direct push) and rely on local Husky pre-push (pnpm prepush:check).

Direct pushes to main still trigger full CI in Deploy frontend to VPS before build/deploy.

Telegram deploy alerts

Add these repository secrets (same values as the monorepo / VPS backend/.env):

  • TELEGRAM_BOT_TOKEN
  • TELEGRAM_GROUP_CHAT_ID
  • TELEGRAM_GROUP_THREAD_ID (optional forum topic)
  • TELEGRAM_CHAT_ID (fallback private chat)

Successful/failed deploys send an admin/backoffice-specific message via scripts/notify-deploy.sh (distinct from the consumer frontend notify copy).