gitea

Commit Graph

Author	SHA1	Message	Date
Jason Song	8cf3b61fb9	Add optimistic lock to ActionRun table (#26563 ) Should fix #26559. How xorm works: https://xorm.io/docs/chapter-06/1.lock/ --------- Co-authored-by: Giteabot <teabot@gitea.io>	1 year ago
Zettat123	48e5a74f21	Support `pull_request_target` event (#25229 ) Fix #25088 This PR adds the support for [`pull_request_target`](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target) workflow trigger. `pull_request_target` is similar to `pull_request`, but the workflow triggered by the `pull_request_target` event runs in the context of the base branch of the pull request rather than the head branch. Since the workflow from the base is considered trusted, it can access the secrets and doesn't need approvals to run.	2 years ago

Author

SHA1

Message

Date

Jason Song

8cf3b61fb9

Add optimistic lock to ActionRun table (#26563 )

Should fix #26559.

How xorm works: https://xorm.io/docs/chapter-06/1.lock/

---------

Co-authored-by: Giteabot <teabot@gitea.io>

1 year ago

Zettat123

48e5a74f21

Support `pull_request_target` event (#25229 )

Fix #25088

This PR adds the support for
[`pull_request_target`](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target)
workflow trigger. `pull_request_target` is similar to `pull_request`,
but the workflow triggered by the `pull_request_target` event runs in
the context of the base branch of the pull request rather than the head
branch. Since the workflow from the base is considered trusted, it can
access the secrets and doesn't need approvals to run.

2 years ago

1 Commits (68d5c18953620927101609bbd21508213cbcd589)