mcpbeat

Pushing CI Changes

openai/pushing-ci-changes

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

223 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
103818
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/openai/codex --skill pushing-ci-changes

The instruction itself

as written by the author

The Codex repository prevents anyone from uploading changes to its CI configuration unless they've

been granted a temporary role.

In order to push changes to .github/**/*.yml and related files you'll need the user to read

go/workflow-approvals and request an approval through that flow. It is not possible for you to

make progress by requesting an exemption yourself.

If you know you're about to push changes that would fail due to these restrictions you should still

try to push anyways to confirm the user's account doesn't already have the necessary approval.

If you encounter a failed push due to these restrictions, share the go/workflow-approvals link with

the user and ask them to return control to you once the approval has propagated to GitHub.

How to use it

Copy the folder

Take openai/pushing-ci-changes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.