pushing-ci-changes

Handles GitHub Actions workflow push rejections by directing users to the approval process.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill pushing-ci-changes-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pushing-ci-changes
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/pushing-ci-changes
Command: npx skills add https://github.com/looooonk/better-codex --skill pushing-ci-changes-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The Codex repository blocks pushes that modify CI configuration files (.github/**/*.yml) unless the user has been granted a temporary approval role, causing confusing push rejections that stall work. ## Core Features & Use Cases - Push Verification: Attempts the push anyway to confirm whether the user's account already has the necessary approval before escalating. - Rejection Handling: Detects failed pushes caused by CI restrictions and shares the go/workflow-approvals link with the user. - Approval Handoff: Instructs the user to request approval through the official flow and return control once it propagates to GitHub. - Use Case: You edit a GitHub Actions workflow file and the push is rejected; the Skill explains the restriction, gives you the approval link, and resumes once your access is granted. ## Quick Start Push my changes to the GitHub Actions workflow file and help me resolve any rejection from the CI configuration restrictions.

Frequently Asked Questions about pushing-ci-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why was my push to a GitHub Actions workflow file rejected?▼

The Codex repository prevents anyone from uploading changes to CI configuration files like .github/**/*.yml unless they have been granted a temporary approval role. The rejection is a repository policy, not a problem with your local Git setup.

How do I get approval to push CI configuration changes?▼

Read the go/workflow-approvals documentation and request an approval through that flow. The approval cannot be requested on your behalf by an automated tool; you must complete the process yourself.

Should I still try pushing workflow changes before requesting approval?▼

Yes, attempt the push first to confirm whether your account already has the necessary approval. If the push succeeds, no further action is needed; if it fails, follow the go/workflow-approvals process.

Can the approval exemption be requested automatically on my behalf?▼

No, it is not possible to make progress by requesting an exemption automatically. You must personally go through the go/workflow-approvals flow and wait for the approval to propagate to GitHub.

What happens after my workflow approval is granted?▼

Once the approval has propagated to GitHub, return control to the assistant and retry the push. The previously rejected changes to the CI configuration files should then upload successfully.