Certain fixes touching workflow files cannot be committed

Open
#99 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@muspi-merol-review is already working on this.

Since Nov 16, 2026.

  • #102 by @muspi-merol-review — open
  • #105 by @CNSeniorious000 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
github, github-actions, typescript
Domain
ci-cd, devtools

Research direction

Read README.md:140 and scripts/instructions.sh:19 to compare the app permissions with the review prompt, then inspect scripts/commit-fix.sh and scripts/open-pr.sh to confirm how fixes are written. Decide whether workflow fixes should be report-only or the app should receive Workflows: write; done means workflow fixes no longer fail silently at commit or PR creation.

Written by the indexing model from the issue text.

Description

bug

The App has no Workflows: write (README.md:140), but the review prompt tells Codex to commit any fix it is certain of (scripts/instructions.sh:19) and to open out-of-scope fixes as PRs. A fix that includes .github/workflows/* cannot land: GitHub rejects commits that create or update workflow files without that permission, and scripts/commit-fix.sh and scripts/open-pr.sh both write through the Git data API.

The reviewer only learns this after the commit or ref creation fails, and a correct workflow fix is left unapplied.

Either say in the prompt that workflow fixes are report-only, or grant Workflows: write if committing them is intended.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1h 39m
Merged PRs (30d)
84

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from promplate/code-review

All issues in promplate/code-review

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.