Git exposes powerful graph mutation operations
  + repository state is often invisible
  + team policies live in human memory
  + CI/review tools hide some graph details
  + people work under interruption and urgency
  = predictable human mistakes

 git config --global alias.st 'status --short --branch'
 git config --global alias.graph 'log --oneline --decorate --graph --all --date-order'
 git config --global alias.last 'log -1 --stat'
 git config --global alias.where 'rev-parse --abbrev-ref HEAD'
 git config --global alias.up 'rev-parse --abbrev-ref --symbolic-full-name @{u}'

git status --short --branch
git log --oneline --decorate --graph --max-count=20
git branch -vv
git remote -v

# sebelum rebase
git status --short --branch
git log --oneline --decorate --graph --boundary @{u}...HEAD

# sebelum force push
git fetch origin
git log --oneline --decorate --graph origin/my-branch..HEAD
git log --oneline --decorate --graph HEAD..origin/my-branch

# sebelum cleanup
git clean -ndx

# Pull tidak diam-diam merge jika belum disepakati tim.
git config --global pull.ff only

# Push hanya current branch ke branch dengan nama sama.
git config --global push.default simple

# Prune remote-tracking branch yang sudah hilang saat fetch.
git config --global fetch.prune true

# Conflict resolution reuse untuk conflict berulang.
git config --global rerere.enabled true

# Bantu conflict marker lebih informatif.
git config --global merge.conflictStyle zdiff3

git reset --hard
git clean -fdx
git push --force
git rebase shared-branch
git tag -f
git push --mirror
git filter-repo / filter-branch
git gc --prune=now
git branch -D

# Jangan buat alias reset-hard yang terlalu pendek.
# Buat alias yang memaksa user membaca state dulu.
git config --global alias.danger-hard-reset '!f() { \
  echo "Current branch:"; git status --short --branch; \
  echo; echo "Last commits:"; git log --oneline --decorate -5; \
  echo; echo "Use: git reset --hard <target> only if you are sure"; \
}; f'

# Force push harus lease-based.
git config --global alias.push-lease 'push --force-with-lease'

# Clean harus dry-run dulu.
git config --global alias.clean-preview 'clean -ndx'

- `git push --force` is prohibited on shared branches.
- `git push --force-with-lease` is allowed only for private PR branches.
- Release tags are immutable after publication.
- History rewrite requires incident/change record.

#!/usr/bin/env bash
set -euo pipefail

if git diff --cached --name-only | grep -E '(^|/)\.env$'; then
  echo "Refusing to commit .env file" >&2
  exit 1
fi

if git diff --cached --check; then
  exit 0
else
  echo "Whitespace error found" >&2
  exit 1
fi

No direct push to main.
No unsigned release tag.
No update to refs/tags/v* after publication.
No merge unless CI validated merge result.
No release branch update without release owner approval.

To update your branch:
run git pull --rebase

## Update private PR branch from main

Use this when:
- your branch is private
- no one else is basing work on it
- you want linear patch series for review

Commands:
```bash
git fetch origin
git rebase origin/main

git reflog
git reset --hard HEAD@{1}

## Amend last commit before pushing

Precondition:
- commit has not been pushed to shared branch

Command:
```bash
git add <files>
git commit --amend

git log -1 --stat

git reflog
git reset --hard HEAD@{1}

Here are the states Git can be in, and how to read them.

git pull

fetch + merge
fetch + rebase
fetch + fast-forward only
fetch from configured upstream
integrate into current branch

fix
new-changes
test
final
release

feature/case-reopen-transition
fix/authz-appeal-officer-scope
hotfix/2026-07-appeal-report-null-actor
release/2026.07.0

[pull]
  ff = only
[push]
  default = simple
[fetch]
  prune = true
[rerere]
  enabled = true
[merge]
  conflictStyle = zdiff3
[branch]
  sort = -committerdate
[tag]
  sort = -version:refname
[diff]
  algorithm = histogram
[init]
  defaultBranch = main

git config --global alias.s 'status --short --branch'
git config --global alias.lg 'log --oneline --decorate --graph --all --date-order'
git config --global alias.out 'log --oneline @{u}..HEAD'
git config --global alias.in 'log --oneline HEAD..@{u}'
git config --global alias.diverge '!f() { git fetch ${1:-origin}; git log --oneline --decorate --left-right --graph HEAD...@{u}; }; f'
git config --global alias.unstage 'restore --staged'
git config --global alias.discard 'restore'
git config --global alias.pushf 'push --force-with-lease'
git config --global alias.cleanup-preview 'clean -ndx'

# Bad: too short for destructive command
git config --global alias.rh 'reset --hard'
git config --global alias.cf 'clean -fdx'
git config --global alias.pf 'push --force'

Alias for safe inspection may be short.
Alias for destructive mutation should be verbose or frictionful.

Use IDE for simple staging/diff/review.
Use CLI for rebase, force-with-lease, release tags, incident recovery, history rewrite, and multi-remote operations.

# saat harus pindah context
git status --short --branch
git diff
git diff --staged
git stash push -u -m "WIP: appeal report refactor before incident call"

# atau lebih baik untuk task paralel
git worktree add ../repo-hotfix hotfix/appeal-report-null-actor

1. Stop non-essential merges.
2. Create incident branch from known good/current target.
3. Snapshot current refs.
4. Make minimal fix.
5. Review with domain + release owner.
6. Verify exact commit to deploy.
7. Tag or record artifact provenance.
8. Backport/forward-port intentionally.
9. Post-incident cleanup.

git fetch origin --tags
git switch -c hotfix/INC-1234-appeal-report origin/main
git status --short --branch
# edit minimal fix
git add -p
git commit -m "fix(report): handle missing appeal actor"
git log -1 --stat
git push -u origin hotfix/INC-1234-appeal-report

During incident, reduce graph creativity.
Prefer minimal commits, explicit branch names, owner review, and revertable changes.

Updated after review:
- split migration into additive + backfill
- renamed policy class only; no behavior change
- added regression test for CLOSED -> APPEAL transition

Range-diff: previous HEAD abc123..def456 vs new HEAD fedcba..987654

Invariant 1: main is always releasable or quickly revertable.
Invariant 2: public release tags are immutable.
Invariant 3: every production artifact maps to exact commit SHA.
Invariant 4: every high-risk path has an owner.
Invariant 5: shared branch history is not rewritten without coordination.
Invariant 6: PR must be reviewable by humans, not merely pass CI.
Invariant 7: incident hotfixes are minimal and backported deliberately.

Use squash merge because we like clean history.

Use squash merge for product feature PRs because our release notes and revert workflow operate at PR-level, not commit-series level. Do not squash maintenance backport series where individual cherry-picks must remain traceable.

1. Repository model
2. Branch naming
3. Commit standard
4. PR standard
5. Review routing / CODEOWNERS
6. Merge method policy
7. Pull/update policy
8. Force-push policy
9. Release branch/tag policy
10. Incident hotfix workflow
11. Recovery playbooks
12. CI checkout assumptions
13. Large file/LFS policy
14. Submodule/subtree policy if used
15. Common failure modes

- Why this policy exists
- When to use it
- When not to use it
- Exact commands
- Verification commands
- Recovery commands
- Escalation path

[ ] Is current branch protected?
[ ] Is working tree dirty?
[ ] Is upstream configured?
[ ] Is branch ahead/behind upstream?
[ ] Are there unpushed commits?
[ ] Is repo shallow?
[ ] Are tags fetched?
[ ] Are submodules clean?
[ ] Is sparse checkout active?
[ ] Is HEAD detached?
[ ] Is Git version supported?

Repository health:
  branch: feature/appeal-report
  upstream: origin/feature/appeal-report
  ahead: 3
  behind: 1
  working tree: dirty
  staged: yes
  untracked: yes
  shallow: no
  submodules: clean

Risk:
  - branch diverged from upstream
  - working tree has uncommitted changes

Suggested next steps:
  - commit or stash local changes before rebase
  - fetch and inspect divergence

[pull]
  ff = only
[push]
  default = simple
[fetch]
  prune = true
[rerere]
  enabled = true
[merge]
  conflictStyle = zdiff3
[alias]
  s = status --short --branch
  lg = log --oneline --decorate --graph --all --date-order
  out = log --oneline @{u}..HEAD
  in = log --oneline HEAD..@{u}
  pushf = push --force-with-lease
  cleanup-preview = clean -ndx

git config --global include.path ~/.gitconfig-team-safe

git config --global --get pull.ff
git config --global --get push.default
git config --global --get alias.pushf

#!/usr/bin/env bash
set -euo pipefail

branch=$(git rev-parse --abbrev-ref HEAD)
upstream=$(git rev-parse --abbrev-ref --symbolic-full-name '@{u}' 2>/dev/null || true)

if [[ "$branch" == "main" || "$branch" == release/* ]]; then
  echo "Refusing force push preflight on protected-like branch: $branch" >&2
  exit 1
fi

if [[ -z "$upstream" ]]; then
  echo "No upstream configured for $branch" >&2
  exit 1
fi

git fetch "${upstream%%/*}"

echo "Branch: $branch"
echo "Upstream: $upstream"
echo
echo "Commits only local:"
git log --oneline "$upstream"..HEAD || true
echo
echo "Commits only upstream:"
git log --oneline HEAD.."$upstream" || true
echo
echo "If this is a private PR branch and the output is expected, use:"
echo "  git push --force-with-lease"

## Summary

## Why this is needed

## Change type
- [ ] behavior change
- [ ] refactor only
- [ ] database migration
- [ ] public API/schema change
- [ ] config/infra/CI change
- [ ] security/authz change
- [ ] release/backport/hotfix

## Risk and ownership
- Domain owner concern:
- Security concern:
- DB concern:
- Operational concern:
- Compliance/audit concern:

## Verification

## Rollback

## Notes for reviewers