Problem when adding a workspace

[joshka]

In ilai-deutel/kibi#328 (comment)

Run mbrobbel/rustfmt-check@master
  with:
    token: ***
    mode: review
    commit-message: Format Rust code using rustfmt
  env:
    CARGO_TERM_COLOR: always
/home/runner/.cargo/bin/cargo +nightly fmt -- --emit json
[]
[]
Error: Unexpected non-whitespace character after JSON at position 2

I then changed the config to include a --package cargo arg and god:

Run mbrobbel/rustfmt-check@master
  with:
    token: ***
    mode: review
    args: --package kibi
    commit-message: Format Rust code using rustfmt
  env:
    CARGO_TERM_COLOR: always
/home/runner/.cargo/bin/cargo +nightly fmt --package kibi -- --emit json
[]
Error: Resource not accessible by integration

Both problems seem like bugs (either in rustfmt nightly or in this action, but I'm not sure which).
Any ideas on how to proceed on this?

[mbrobbel]

Thanks for reporting.

This looks like a GitHub actions permission issue. I'll take a look.

[mbrobbel]

Looks like this is happening on a PR from a forked repo. Depending on the repo configuration the token may not get the required write permissions, resulting in the Resource not accessible by integration error. More info here https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token.

Can you maybe rerun the failed job and select Enable debug logging.?

[joshka]

Makes sense. Thanks for taking a look. I'm not the repo owner on this one. I'll let the owner know.

[ilai-deutel]

Hi, I just reran the failed job with debug logging, here are the logs: https://gist.github.com/ilai-deutel/67505c1b914805ee2a737c2c33a9c55f

Interestingly, it says:

2024-11-15T14:50:20.3867907Z ##[group]GITHUB_TOKEN Permissions
2024-11-15T14:50:20.3869683Z Checks: read
2024-11-15T14:50:20.3870080Z Metadata: read
2024-11-15T14:50:20.3870600Z PullRequests: read
2024-11-15T14:50:20.3870976Z ##[endgroup]

even though the workflows have "Read and write permissions" and "Allow GitHub Actions to create and approve pull requests" in the project setting, and the action config has:

permissions:
  pull-requests: write
  checks: write

Run

[mbrobbel]

To make this work, a repo admin must set the (non-default) configuration required to get write permissions for workflows from forks. However, following the principle of least privilege, this is not something I recommend.

Maybe this action should switch to anntations (instead of review comments) when review mode is enabled but the workflow is triggered from a fork?

[ilai-deutel]

@mbrobbel Yes I think an annotation mode would be great!

[mbrobbel]

@mbrobbel Yes I think an annotation mode would be great!

I created #1140 to track this addition.