코드는 내 컴퓨터에 두고
잘못된 푸시는 되돌립니다.

$ owngit backup --output ~/Backups/owngit-backup
Offline backup written to ~/Backups/owngit-backup. SHA-256 hashes detect
 corruption but do not authenticate a replaced backup.
$ owngit restore --input ~/Backups/owngit-backup --state-dir ~/restored-
state --repository-root ~/restored-repositories
Offline backup restored to ~/restored-state with repositories at ~/resto
red-repositories. Previous sessions, trusted hosts, and network settings
 were not restored.

$ owngit network show
Saved settings (used at the next start; a serve flag overrides one for t
hat run):
  Listen address: 127.0.0.1:18432
  Base URL:       not saved, addresses follow the address each client us
es
  Allowed Hosts:  none
  localhost, 127.0.0.1 and ::1 are always accepted.
  Trusted proxies: none
Running server (process 70198, started 2026-09-26T14:43:26Z):
  Listen address: 127.0.0.1:18432 (saved), listening on 127.0.0.1:18432
  Base URL:       none, addresses follow the address each client uses (d
efault)
  Accepted Hosts: 127.0.0.1, ::1, localhost
  Trusted proxies: none (default)
The running server uses the saved settings.
$ owngit tailscale status
Sharing on the tailnet over HTTPS: off.
  Tailscale: ~/demo/bin/tailscale
  Ready to share as https://sample-host.example-tailnet.ts.net/.
Turn it on with "owngit tailscale on", or in Settings.
$ owngit tailscale on
When Tailscale issues the certificate for this address, the names of thi
s computer and your tailnet, as in sample-host.example-tailnet.ts.net, a
re recorded in a public certificate log. Only the fact that the address
was opened is recorded, not your code, repositories, passwords or other
content. To use another name, change it in the Tailscale admin console b
efore turning sharing on. Names that already got a certificate stay in t
he log, even after a rename.
Tailscale now answers HTTPS for sample-host.example-tailnet.ts.net and p
asses it to OwnGit at http://127.0.0.1:18432.
Saved: base URL https://sample-host.example-tailnet.ts.net, allowed name
 sample-host.example-tailnet.ts.net, trusted proxy 127.0.0.1.
Sharing on the tailnet over HTTPS: on, but not ready yet.
  Address:   https://sample-host.example-tailnet.ts.net/ (encrypted by T
ailscale on this computer)
  Clone URL: https://sample-host.example-tailnet.ts.net/git/REPOSITORY.g
it
  Tailscale: ~/demo/bin/tailscale
  Restart OwnGit to finish. The running server does not use the new sett
ings yet.
This command cannot change a running OwnGit, so the change applies after
 a restart. Turning sharing on or off in Settings applies at once.

$ owngit pr create --source feature/sitemap --target main --title "Add s
itemap" --accept-insecure-http | jq '.pull_request | {number, title, sta
te}'
owngit: using server http://127.0.0.1:18432 and repository website from
the origin remote
{
  "number": 1,
  "title": "Add sitemap",
  "state": "open"
}
$ owngit pr diff --number 1 --stat --accept-insecure-http | jq -c '.sour
ce, .target, .files[]'
owngit: using server http://127.0.0.1:18432 and repository website from
the origin remote
{"branch":"feature/sitemap","oid":"c89e0e2aefe2cfcc798829cbc10bcdb38bda1
574"}
{"branch":"main","oid":"f744962ea89f44bf26b7342f9dc271f33acee085"}
{"path":"sitemap.xml","status":"added","additions":2,"deletions":0,"bina
ry":false}
$ owngit pr merge --number 1 --source-oid c89e0e2aefe2cfcc798829cbc10bcd
b38bda1574 --target-oid f744962ea89f44bf26b7342f9dc271f33acee085 --accep
t-insecure-http | jq -c '.pull_request | {state, merge: .merge.mode}'
owngit: using server http://127.0.0.1:18432 and repository website from
the origin remote
{"state":"merged","merge":"fast_forward"}

$ cat ~/.codex/config.toml
[mcp_servers.owngit]
command = "owngit"
args = ["mcp", "--workdir", "~/website", "--credential-file", "~/helper-
token", "--accept-insecure-http"]
tool_timeout_sec = 1800
$ codex exec --ephemeral --skip-git-repo-check -m gpt-5.6-luna -c 'model
_reasoning_effort="low"' -c 'mcp_servers.owngit.default_tools_approval_m
ode="approve"' 'Use the owngit tools. List the repositories. Open a pull
 request from feature/sitemap into main titled "Add sitemap" and show it
s diff stat. Create a check task and run the checks. If they pass, appro
ve the pull request with the reviewer label "codex" and merge it. Answer
 in English in two short sentences.'
OpenAI Codex v0.157.0
--------
workdir: ~/project
model: gpt-5.6-luna
provider: openai
approval: never
sandbox: read-only
reasoning effort: low
reasoning summaries: none
session id: 01a0dbaf-11a2-7d83-b1e8-42cccbdf4ef6
--------
user
Use the owngit tools. List the repositories. Open a pull request from fe
ature/sitemap into main titled "Add sitemap" and show its diff stat. Cre
ate a check task and run the checks. If they pass, approve the pull requ
est with the reviewer label "codex" and merge it. Answer in English in t
wo short sentences.
codex
I’m using the OwnGit repository tools to list repositories, open the pul
l request, run its checks, and merge it if everything passes.
mcp: owngit/repository_list started
mcp: owngit/repository_list (completed)
mcp: owngit/pull_request_create started
mcp: owngit/pull_request_create (completed)
mcp: owngit/check_task_create started
mcp: owngit/check_task_create (completed)
mcp: owngit/pull_request_diff started
mcp: owngit/pull_request_diff (completed)
mcp: owngit/check_run started
mcp: owngit/check_run (completed)
mcp: owngit/pull_request_review started
mcp: owngit/pull_request_review (completed)
mcp: owngit/pull_request_merge started
mcp: owngit/pull_request_merge (completed)
codex
Listed the `website` repository; PR #1 “Add sitemap” has a 2-file, 14-li
ne diff. Checks passed, it was approved by `codex`, and merged into `mai
n`.
tokens used
20,918