4 Commits

• chore(rs): update dependencies (#1494)

  ### Chores
  - Update cargo dependencies
  - Remove unused cargo dependencies
  - Fix clippy warnings
  - Update Dockerfile (package.json requires node 22)
  - Let Dependabot update bun, cargo, devcontainers, docker,
  github-actions, npm (nix still not supported)
  
  ### TODO
  - Upgrade dependencies with breaking changes
  
  ```shell
  $ cargo update --verbose
     Unchanged crossterm v0.28.1 (available: v0.29.0)
     Unchanged schemars v0.8.22 (available: v1.0.4)
  ```

  Rene Leonhardt · 2025-07-10 11:08:16 -07:00
  82b0cebe8b
• fix: missed a step in #1171 for codex.yml (#1172)

  Missed in my copy/paste.

  Michael Bolin · 2025-05-30 11:04:41 -07:00
  0f40ef5a10
• fix: update outdated repo setup in codex.yml (#1171)

  We should do some work to share the setup logic across `codex.yml`,
  `ci.yml`, and `rust-ci.yml`.

  Michael Bolin · 2025-05-30 10:58:57 -07:00
  8676185389
• feat: initial import of experimental GitHub Action (#1170)

  This is a first cut at a GitHub Action that lets you define prompt
  templates in `.md` files under `.github/codex/labels` that will run
  Codex with the associated prompt when the label is added to a GitHub
  pull request.
  
  For example, this PR includes these files:
  
  ```
  .github/codex/labels/codex-attempt.md
  .github/codex/labels/codex-code-review.md
  .github/codex/labels/codex-investigate-issue.md
  ```
  
  And the new `.github/workflows/codex.yml` workflow declares the
  following triggers:
  
  ```yaml
  on:
    issues:
      types: [opened, labeled]
    pull_request:
      branches: [main]
      types: [labeled]
  ```
  
  as well as the following expression to gate the action:
  
  ```
  jobs:
    codex:
      if: |
        (github.event_name == 'issues' && (
          (github.event.action == 'labeled' && (github.event.label.name == 'codex-attempt' || github.event.label.name == 'codex-investigate-issue'))
        )) ||
        (github.event_name == 'pull_request' && github.event.action == 'labeled' && github.event.label.name == 'codex-code-review')
  ```
  
  Note the "actor" who added the label must have write access to the repo
  for the action to take effect.
  
  After adding a label, the action will "ack" the request by replacing the
  original label (e.g., `codex-review`) with an `-in-progress` suffix
  (e.g., `codex-review-in-progress`). When it is finished, it will swap
  the `-in-progress` label with a `-completed` one (e.g.,
  `codex-review-completed`).
  
  Users of the action are responsible for providing an `OPENAI_API_KEY`
  and making it available as a secret to the action.

  Michael Bolin · 2025-05-30 10:55:28 -07:00
  baa92f37e0