Git author + branch rules — ABSOLUTE
User directive 2026-04-30 (r_goto). Updated 2026-05-03 with corrected per-workspace identity.
Author per workspace (verified 2026-05-03)
| Workspace | Persona | git user.name | git user.email |
|---|---|---|---|
/var/www/corone.monster | Ryo | Corone - Ryo | 277812962+eduson510@users.noreply.github.com |
/var/www/kebahagiaan.corone.monster | Julian | Julian Loh - ロジュリアン | 123628335+time7676@users.noreply.github.com |
Active branches (2026-05-03)
| Workspace | Current branch | Purpose |
|---|---|---|
| corone.monster | corone-ryo | Ryo personal customization |
| kebahagiaan.corone.monster | corone-julian | Julian personal customization (Hermes Self-Healing Port author) |
Legacy release/corone + release/kebahagiaan branches still exist (pre-personal-fork era).
Branch naming
Generic format: <type>/<JIRA-ID>-<task-slug-en>
- type: feature / fix / chore / refactor / hotfix / docs
- Jira ID: CRV-XX, KOKO-XX, PASS-XX, PL-XX, RMY-XX, SL-XX (NEVER
DVG-XX— see jira-da-vinci-no-touch) - Task slug: kebab-case English, 3–7 words
- If user hasn’t given Jira ID → ASK, never invent
Curva-specific override: user/corone-CRV-XX-Task-name from develop — see curva-github-practice.
Pasukuru convention (observed): <JIRA-ID>-<task-slug> directly under dev (e.g. PASS-121-stripe-receipt-tax-and-paypay-integration).
Push workflow rules — ABSOLUTE
- NEVER edit directly on protected branches: main / master / develop / staging / production / release/*. Always create new branch first.
- New branch every PR — never reuse old branches for new work.
- Jira ID required in: branch name, commit msg, PR title, PR body. NO Jira ID → create one in Jira FIRST (except DVG project — never create).
- Workspace attribution in PR body + Jira comment: “Requested by Ryo” (corone) or “Requested by Julian” (keb).
- Stage files by name — never
git add .. - Never commit secrets.
- Quick fix exception ban — even one-line / hotfix / urgent: STILL new branch + Jira ID. Override only on EXPLICIT verbatim user instruction; log override to
.wiki/log.md.
After push — REQUIRED post-actions
A) mcp__jira__jira_add_comment on the Jira ticket with: 1-2 sentence overview, files touched list, PR/commit link, workspace attribution.
B) MemorySave (scope=all, category=global) with: id jira-<KEY>-<short-slug>, title [JIRA-KEY] short title, content same as Jira comment, tags include jira, project key, workspace, push-log.
Merge gate
PR creation OK without asking. MERGE forbidden without explicit user approval. NEVER run gh pr merge, git merge to protected branch, force push to protected branch. Wait for verbatim “merge it” / “approved”.
Cross-refs
- github-account-routing — per-workspace GitHub account binding
- curva-github-practice — Curva-specific overrides
- jira-da-vinci-no-touch — DVG project no-touch rule