AliSaZa/admin
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
e1eaf5eff5
admin/.github/BRANCH_PROTECTION.md
alisaza e1eaf5eff5 feat: initial ghabilee-admin backoffice app 
Extract admin dashboard from ghabilee-frontend2 into a dedicated Next.js
app for backoffice.ghabilee.ir (no SEO indexing / Clarity).
2026-09-05 13:12:59 +03:30

1.2 KiB
Raw Blame History

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 a frontend-specific message via scripts/notify-deploy.sh.