Skip to content
This repository was archived by the owner on Oct 13, 2023. It is now read-only.
This repository was archived by the owner on Oct 13, 2023. It is now read-only.

Access pemissions problems are not prominent in the README.md #19

@martinfrances107

Description

@martinfrances107

I just want given feedback after getting this to work...

I had a persistent problems until I overrode the default permissions.
I think it critical to mention this in the use guide ( README.md ) otherwise nothing works.

This is the error report has permission denied errors.

error: failed to open: /home/runner/work/rust_d3_geo/rust_d3_geo/target/debug/.cargo-lock

Caused by:
  Permission denied (os error 13)
Oct 27 09:54:47.443  INFO cargo_tarpaulin::report: Coverage Results:
Oct 27 09:54:47.443 ERROR cargo_tarpaulin::report: Failed to create report directory: Permission denied (os error 13)

After I read this, and saw write permission is in general not given

You can use the permissions key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the Send write tokens to workflows from pull requests option in the GitHub Actions settings. For more information, see "[Managing GitHub Actions settings for a repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."

Following the link show me what radio buttons to set.

I am just going to write a PR that updates the README.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions