Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →deonmenezes/pushing-ci-changes
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
and 7 more in the full report
13 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I need to push a commit touching .github/workflows/release-notes.yml. Git rejected the push due to CI configuration lockdown. What link should I provide to the team member who needs to grant access?
| Checked | Without skill | With skill |
|---|---|---|
| The response includes the go/workflow-approvals link. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.