Skip to content

docs(codex): point GitLab readers to maintained guidance #3031

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fwph-oai merged 2 commits into from
Aug 31, 2026
+2 −0
Merged

docs(codex): point GitLab readers to maintained guidance #3031

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a96e3c3
docs(codex): point GitLab readers to maintained guidance
fwph-oai Aug 27, 2026
7e16f31
Merge branch 'main' into docs/gitlab-cookbook-current-guidance
fwph-oai Aug 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions examples/codex/secure_quality_gitlab.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Automating Code Quality and Security Fixes with Codex CLI in GitLab

> **Update note — review the current guidance before using these examples.** The `--full-auto` flag used below is deprecated. Do not treat a failed Codex run or invalid output as an empty findings result. For general Codex automation, see [Non-interactive mode](https://learn.chatgpt.com/docs/non-interactive-mode). For dedicated Codex Security scanning and remediation, use the maintained [GitLab CI/CD guide](https://learn.chatgpt.com/docs/security/cli/ci/gitlab). That workflow differs from this article's code-quality analysis and interpretation of existing SAST results; the examples below have not been migrated to it.

## Introduction

When deploying production code, most teams rely on CI/CD pipelines to validate changes before merging. Reviewers typically look at unit test results, vulnerability scans, and code quality reports. Traditionally, these are produced by rule-based engines that catch known issues but often miss contextual or higher-order problems—while leaving developers with noisy results that are hard to prioritize or act on.
Expand Down
Loading