# Codex Features and Practical Usage ⚙️ Review the moment a PR opens, ship a scheduled report every morning — run Codex as a single workflow step and the automation lives entirely in CI. 🏷️ Title: Actions Execution (Codex GitHub Action) 🔗 URL: 📘 Overview The Codex GitHub Action (`openai/codex-action@v1`) is the official action for running Codex from GitHub Actions workflows. It installs the Codex CLI, configures API access, and runs `codex exec` for you, keeping code review, quality gates, and scheduled reports entirely inside CI. ⚙️ How It Works Store your OpenAI key as a GitHub secret (e.g. `OPENAI_API_KEY`) and check out the code before invoking the action. Key inputs: ・`prompt` / `prompt-file`: inline instructions or a prompt file in the repo (pick one). ・`model` / `effort`: choose the model and the work intensity. ・`sandbox`: `read-only` / `workspace-write` / `danger-full-access` control filesystem and network access. ・`codex-args`: extra CLI flags as a JSON array or shell string. ・`output-file`: save the final message to upload as an artifact. The `safety-strategy` input defaults to `drop-sudo` (irreversibly removes sudo); other options are `unprivileged-user` and `unsafe`, which Windows runners require. Results are exposed via the `final-message` output. 🛠️ Practical Usage A minimal review workflow triggers on `pull_request` (types `opened`, `synchronize`), checks out the code with `actions/checkout@v5`, then runs `openai/codex-action@v1` with `openai-api-key` from secrets, a `prompt-file`, and an `output-file`. To post the result as a PR comment, pass the `final-message` output to `actions/github-script` in a downstream job (which needs `pull-requests: write`). 💡 Use Cases Use `pull_request` triggers for review and quality gates, `schedule` (cron) for periodic reports, `workflow_dispatch` for manual runs, and `issue_comment` for comment-driven automation. ⚠️ Caveats You cannot supply both `prompt` and `prompt-file`. If you ingest PR titles or comments, guard against prompt injection and restrict to trusted events or explicit approvals. Keep `safety-strategy` on `drop-sudo` or an unprivileged user, and place the action at the end of the job to avoid inheriting state. After `drop-sudo` you may need to grant write access (e.g. `chmod -R g+rwX`). #Codex# #GitHubActions#

github actions in my oss repos suddenly stopped running today i had opus 4.8 look into it, it spent ~$10 worth of tokens and insisted that either i haven't paid my bills or there's a github outage switched to grok 4.5 and just 3 minutes in with $1.2 worth of tokens, it found there's a surge of CI runs in my firstmate repos starving all the allowed runners across my account, cancelled a bunch of them, and everything's back on track this is just an anecdotal example but i've had many positive experiences like this. people ask me why i default to grok and this is why

Push images from GitHub Actions to Vercel Container Registry without stored credentials. Use 𝚟𝚎𝚛𝚌𝚎𝚕/𝚟𝚌𝚛-𝚊𝚌𝚝𝚒𝚘𝚗/𝚕𝚘𝚐𝚒𝚗@𝚟𝟷 for short-lived auth via OIDC. Learn more ↓

Announcing StarSling GPU Runners: GitHub Actions runners backed by fast NVIDIA GPUs ⚡️ More and more teams need GPUs for their CI, and those GPUs have to be pulled from training runs or inference. Your GPUs should be used for product, not tests. With StarSling GPU Runners you get dedicated GPUs for your CI jobs with per minute billing. One of our customers is already seeing a 14x reduction in queue time for a GPU runner!

Everyone is always criticizing @GitHub Actions for their outages, but today one of the most popular alternatives @useblacksmith has been experiencing a "partial" outage for the last 8 hours. Before 2026, it was almost unheard of to hear of outages that lasted more than a couple hours, let alone a majority of the day.