What is the problem?
permission denied 报错不能靠盲目提权解决。新手要先判断被拒绝的是文件、目录、SSH、Git、部署平台还是客户授权，再按证据处理。
Quick solution
Treat this as a GitHub troubleshooting 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 guideDetailed steps
- 保存完整命令和完整报错。
- 记录操作系统、终端、当前目录和当前用户。
- 判断被拒绝对象：文件、目录、端口、仓库、SSH key、部署平台还是客户账号。
- 先用只读命令查看状态，例如 `pwd`、`whoami`、`git status`、`git remote -v`。
- 如果是 Git 或 SSH，检查远程地址、账号、key 和仓库权限。
- 如果是部署环境，确认平台允许写入的目录和构建规则。
Commands or code
permission denied 排查记录
完整命令：
完整报错：
操作系统：
终端：
当前目录：
当前用户：
被拒绝资源：
已验证方向：
需要客户授权：
下一步：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.