Skip to content

chore: add Codex setup guidelines#1437

Merged
shm11C3 merged 1 commit into
developfrom
chore/codex-setup-guidelines
May 2, 2026
Merged

chore: add Codex setup guidelines#1437
shm11C3 merged 1 commit into
developfrom
chore/codex-setup-guidelines

Conversation

@shm11C3

@shm11C3 shm11C3 commented May 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add project-local Codex hook configuration under .codex/.
  • Ignore local Codex config.toml from the repository.
  • Document commit message expectations in AGENTS.md.

Details

Commit subjects should follow Conventional Commits. For non-trivial changes, commits should also include a body describing why the change was made, notable implementation details, and validation performed.

Validation

  • jq empty .codex/hooks.json
  • git diff --check

Summary by CodeRabbit

  • Chores

    • Enhanced development tooling configuration with automated code quality checks that run during file operations
    • Expanded repository-level configuration management with improved version control patterns to properly exclude build and configuration artifacts
  • Documentation

    • Added comprehensive git commit guidelines documentation to establish standardized development practices and improve code review clarity

Add project-local Codex hook configuration and document commit message expectations for agent-created changes.

Commit subjects should follow Conventional Commits, and non-trivial changes should include a body describing the motivation, implementation notes, and validation.
@coderabbitai

coderabbitai Bot commented May 2, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: e2889117-7a55-4cbd-acd9-a5a39f3b48f6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • ✅ Review completed - (🔄 Check again to review again)
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/codex-setup-guidelines

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added the docs label May 2, 2026
@shm11C3 shm11C3 marked this pull request as ready for review May 2, 2026 10:25
Copilot AI review requested due to automatic review settings May 2, 2026 10:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR adds repository-local Codex configuration guidance so local AI tooling follows the same Rust formatting/linting workflow already used elsewhere, while also documenting commit message expectations for contributors.

Changes:

  • Add .codex/hooks.json with a post-tool hook that runs Rust formatting and lint checks after Rust file edits.
  • Add .codex/.gitignore so local-only Codex config.toml does not get committed.
  • Document Conventional Commits and recommended commit body content in AGENTS.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
AGENTS.md Adds commit message guidance for contributors and agents.
.codex/hooks.json Introduces shared Codex hook configuration mirroring existing Rust check automation.
.codex/.gitignore Keeps local Codex config out of version control.

@shm11C3 shm11C3 merged commit 3bcf787 into develop May 2, 2026
29 checks passed
@shm11C3 shm11C3 deleted the chore/codex-setup-guidelines branch May 2, 2026 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants