Skip to content

OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security

chore: simplify pull request labels (#1518)

mldangelo-oaif5da341a5158
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index e3abe209e..9b8be0d73 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -1,6 +1,7 @@
version: 2
updates:
- package-ecosystem: npm
+ labels: [dependencies]
directories:
- /github-action
- /sdk/typescript
@@ -39,6 +40,7 @@ updates:
include: scope
- package-ecosystem: pip
+ labels: [dependencies]
directory: /plugins/codex-security
schedule:
interval: cron
@@ -52,6 +54,7 @@ updates:
include: scope
- package-ecosystem: github-actions
+ labels: [dependencies]
directory: /
schedule:
interval: cron
@@ -64,6 +67,7 @@ updates:
prefix: ci
- package-ecosystem: docker
+ labels: [dependencies]
directory: /
schedule:
interval: cron
@@ -75,6 +79,7 @@ updates:
include: scope
- package-ecosystem: cargo
+ labels: [dependencies]
directory: /plugins/codex-security/native
schedule:
interval: cron
@@ -86,6 +91,7 @@ updates:
include: scope
- package-ecosystem: devcontainers
+ labels: [dependencies]
directory: /
schedule:
interval: cron
diff --git a/AGENTS.md b/AGENTS.md
index 2ae08790c..2db86f022 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -105,3 +105,5 @@ attachments, and links for sensitive information.
pull requests before merging them.
- Review material before publishing it. Editing or deleting it afterward does
not guarantee removal from notifications, caches, or public history.
+- Follow the [pull request label policy](CONTRIBUTING.md#pull-request-labels).
+ Keep `area:*` labels on issues, not pull requests.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 6738af3d3..83335097d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -52,6 +52,23 @@ credentials, or sensitive scan results publicly.
If a scan finds a vulnerability in another project, report it to that
project's maintainers through their security policy.
+## Pull request labels
+
+Keep pull request labels focused on release behavior and material platform
+impact. Do not apply `area:*` labels to pull requests; describe the affected
+surface in the title and description. Issues retain their existing area,
+priority, and status labels. Existing maintainer triage labels can remain on
+pull requests while they identify actionable, unresolved work.
+
+Preserve the release labels `bug`, `enhancement`, `documentation`,
+`breaking-change`, and `skip-release-notes`, including maintainer overrides.
+Follow their [release-note and version semantics](RELEASING.md). Do not replace
+manual `breaking-change` or `skip-release-notes` labels based only on the title.
+
+Use `platform:windows` only when Windows-specific behavior is material to the
+change. Dependabot uses `dependencies` across all package ecosystems. Labels
+are not required to open, test, review, or merge a pull request.
+
## Dependency and release maintenance
Maintainers update package dependencies and committed lockfiles with the