Jason Song d92909fa8b

Treat PRs with agit flow as fork PRs when triggering actions. (#23884) ...

There is no fork concept in agit flow, anyone with read permission can
push `refs/for/<target-branch>/<topic-branch>` to the repo. So we should
treat it as a fork pull request because it may be from an untrusted
user.

2023-04-06 16:57:30 -04:00

..

run_job_list.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

run_job.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

run_list.go

Require approval to run actions for fork pull request (#22803)

2023-02-24 15:58:49 +08:00

run.go

Treat PRs with agit flow as fork PRs when triggering actions. (#23884)

2023-04-06 16:57:30 -04:00

runner_list.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

runner_token.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

runner.go

Display the version of runner in the runner list (#23490)

2023-03-19 22:19:40 -04:00

status.go

Require approval to run actions for fork pull request (#22803)

2023-02-24 15:58:49 +08:00

task_list.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

task_step.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

task.go

Avoid too long names for actions (#23162)

2023-02-28 18:20:36 +08:00

utils_test.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00

utils.go

Implement actions (#21937)

2023-01-31 09:45:19 +08:00