Codex Github Workflow Freelance Scope: quick fix, steps, and deep guide

Q: Codex Github Workflow Freelance Scope

Treat this as a Codex case-study issue. Confirm the environment, inputs, permissions, logs, and delivery boundary, then use the linked deep guide for the full checklist.

What is the problem?

给 AI 工具新手的 Codex + GitHub 项目范围判断指南：如何区分普通代码提交、高风险仓库权限、CI/部署变更，并把分支、PR、验证和客户确认写进报价。

Quick solution

Treat this as a Codex case-study issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.

Read the deep guide

Detailed steps

仓库是公开还是私有？访问权限由谁授权？
是否有指定分支？是否允许创建新分支？
是否要求 PR，还是客户只需要补丁文件？
项目有哪些检查命令？
CI 是否必须通过？
是否会自动触发部署？

Commands or code

本次范围：
- 基于客户授权仓库创建任务分支
- 完成约定文件范围内的修改
- 运行约定检查命令
- 提供提交记录或 PR 描述
- 标明未覆盖范围和客户待确认事项

不包含：
- 合并主分支
- 生产部署
- 修改 GitHub secrets 或账号权限
- 处理真实生产密钥和用户数据

Risk notes

Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.