How Codex CLI imports osFoundry files into GitNest and publishes a pull request
In the end, Codex CLI can perform two tasks in a GitNest repository on osFoundry. It writes files from your terminal session to a branch, and it outputs a finished change set as a pull request, either directly to GitNest or as a draft on GitHub or GitLab. Codex itself does not commit or push anything. Each task appears as a card under "Needs your approval" on the…
Codex CLI can perform two tasks in a GitNest repository on osFoundry. It can write files from a terminal session to a branch and create a pull request. The tasks appear as cards under "Needs your approval" in the Codex CLI connection, requiring the repository owner's approval before any action is taken. The owner can approve or decline the proposed changes, and Codex CLI does not commit or push changes itself.
Codex holds an osFoundry OAuth token with read and write permissions, and the repository owner must have granted access to Codex CLI.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
