Skip to content

Distant test on auto-assign.yml & project-status.yml #201

@TVW96

Description

@TVW96

The original PR for the update to this file only edited two lines of code. Testing this feature seemed to be impossible without first merging the branch, so I suggested merging and scheduling a distant test after all other PR's have been resolved.

Here is the original PR description:

Edge case discovered with workflow script.
Forked repos triggering a failure.
pull_request -> pull_request_target
This trigger runs in the context of the base repository, so it has access to secrets even for fork PRs

Before resolving this issues please test the auto-assign feature to assure it works for forked-repos.

Link to original PR's:
#171
#170

Metadata

Metadata

Assignees

No one assigned

    Labels

    DevOpsCI/CD pipelines, build, and release management

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions