39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
# Codex Online GitOps Version Management
|
|
|
|
Codex is configured to treat the online Git baseline as the version source of truth.
|
|
|
|
- Workspace: `/data/aios-gitops/workspace`
|
|
- Git web: `https://cnnetmkt.top/git/aios/aios-v23`
|
|
- API base: `https://cnnetmkt.top/api`
|
|
- OpenAPI schema: `https://cnnetmkt.top/api/openapi-chatgpt-actions.yaml`
|
|
- Runtime token account: `codex-gitops-bot`
|
|
- Runtime token ref: `secret_ref://aios-gitops/runtime/codex-gitops-bot`
|
|
|
|
## Rules
|
|
|
|
1. Codex updates must use Git patch branches; ZIP upload is deprecated.
|
|
2. Every Codex write must become a Git commit.
|
|
3. Codex must not push directly to `main`; merge to `main` requires owner/admin approval.
|
|
4. V-level release/tag/rollback requests must not bypass owner/admin approval.
|
|
5. User custom LLM API keys must stay in runtime secrets and enter Git only as `secret_ref`.
|
|
6. Test or acceptance branches can remain as audit evidence, but dummy model/provider configs must not be merged into production `main`.
|
|
|
|
## Standard Flow
|
|
|
|
```text
|
|
main -> patch/<name> -> commit -> diff review -> smoke test -> owner/admin approval -> merge main -> VxRxCx tag -> baseline/current.json
|
|
```
|
|
|
|
## Current Merge
|
|
|
|
`V1R1C1` merges the current GitOps/ChatGPT/Codex access changes into the latest online baseline while excluding acceptance dummy model configuration.
|
|
|
|
## Online Git Sync
|
|
|
|
Starting in `V1R1C3`, committed API/Codex patch branches are synchronized from the workspace clone into the online Gitea bare repository. Protected production branches remain excluded from API sync.
|
|
|
|
## Codex and Custom GPT Collaboration Test
|
|
|
|
`V1R1C3` confirms local Codex and the custom GPT Actions path can independently create patch branches, commit files, sync to online Git, and then merge into the latest baseline version.
|
|
|