Skip to content

[codex] Improve open source documentation governance#5

Merged
Pigbibi merged 1 commit into
mainfrom
codex/docs-governance-20260603
Jun 3, 2026
Merged

[codex] Improve open source documentation governance#5
Pigbibi merged 1 commit into
mainfrom
codex/docs-governance-20260603

Conversation

@Pigbibi
Copy link
Copy Markdown
Contributor

@Pigbibi Pigbibi commented Jun 3, 2026

Summary

  • add or link standard open-source governance docs from the README
  • add CODE_OF_CONDUCT across the repository surface
  • add missing CONTRIBUTING and SECURITY docs where this repository did not already have them

Validation

  • git diff --check
  • Markdown link check across repository docs

@Pigbibi Pigbibi merged commit 7912f29 into main Jun 3, 2026
@Pigbibi Pigbibi deleted the codex/docs-governance-20260603 branch June 3, 2026 10:55
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 95f367cf4b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread SECURITY.md
Comment on lines +17 to +18
- Contact the maintainer directly at GitHub: `@Pigbibi`.
- If private vulnerability reporting is enabled for this repository, prefer that channel.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Provide an actual private reporting channel

When GitHub private vulnerability reporting is not enabled for this repository, this policy tells reporters not to open a public issue but only gives a GitHub username; GitHub mentions/profile pages are not a guaranteed private contact mechanism. That leaves no actionable confidential path for credential or workflow-token disclosures, so the policy should include a concrete private channel or require enabling GitHub private vulnerability reporting.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant