Problems with self-hosted runners about pull-request HOT 7 CLOSED

Fixed

from pull-request.

@wei thanks, but you fixed only the first problem.
This pr #90 fixes the second problem.

from pull-request.

Can you elaborate and provide reproduction steps?

causes some problems with the files in future runs

from pull-request.

Can you elaborate and provide reproduction steps?

When a container runs, it uses the root user by default, that new files created in a container will be added to a runner with root user permissions.
After the first run, next runs will fail at this step:
- uses: actions/checkout@v3
because a runner is using a different user (not root) and can not clear files with root permission (git clean)

jobs:
  pull-request:
    runs-on: [ self-hosted, Linux ]
    steps:
    - uses: actions/checkout@v3
    - uses: docker://ghcr.io/repo-sync/pull-request:v2.8 
      with:
        destination_branch: "main"
        github_token: ${{ secrets.GITHUB_TOKEN }}

from pull-request.

Same problem here, the workflow cannot run twice. Second run fails to delete files created with the root user by the first run.

from pull-request.

The permission issue with self-hosted runners is a general issue that happens to all docker based actions on self-hosted runners.

You can find discussions, solutions, and provide feedback at actions/runner#434

I'm going to mark this as a wontfix for now but open to revisit in the future.

from pull-request.

Added a section to README: Docker Container Image Usage

from pull-request.