Croway opened a new pull request, #139: URL: https://github.com/apache/camel-upgrade-recipes/pull/139
Closes #133. ## Root cause `comment-pr.yml` has ended in `startup_failure`, with no job created, on every run since **2026-03-20**. It had 44 successful runs up to 2026-03-19. The run page gives the reason (the API does not expose it): > `googleapis/code-suggester@v4` is not allowed in apache/camel-upgrade-recipes because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns: … ASF enforces its GitHub Actions allow-list ([apache/infrastructure-actions](https://github.com/apache/infrastructure-actions)), and `googleapis/code-suggester` is not on it. No other `apache/*` repository uses that action. The `GITHUB_TOKEN` permissions theory in #133 was wrong. ## Why remove instead of fix - No allow-listed action posts review suggestions the way `code-suggester` does. Keeping the bot would mean an allow-list request to ASF Infra for an action only this repository uses, or a hand-written replacement that can only be tested after merge, because `workflow_run` workflows run from `main`. - The patch `receive-pr.yml` uploads is not specific to the PR: `main` itself does not pass the best-practices recipe. The latest patch touched 26 files, most of them unrelated to the PR it ran on. - Nobody noticed that it had stopped posting for about six months. `receive-pr.yml` only existed to produce the `patch` / `pr_number` artifacts for `comment-pr.yml`, so it is removed too. The `openrewrite` Maven profile stays, and the README now points contributors at `mvn -Popenrewrite rewrite:run` without claiming that a GitHub Action runs it on PRs. _Claude Code on behalf of croway_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
