gitea

Commit Graph

Author	SHA1	Message	Date
JakobDev	4636f56e7b	Add Index to `action.user_id` (#27403 ) Another Column that needs a Index. Found at https://codeberg.org/forgejo/discussions/issues/61#issuecomment-1258744. Co-authored-by: Giteabot <teabot@gitea.io>	1 year ago
Lunny Xiao	9c0a3532a4	Add a new column schedule_id for action_run to track (#26975 ) Fix #26971 And the UI now will display it's scheduled but not triggered by a push. <img width="954" alt="图片" src="https://github.com/go-gitea/gitea/assets/81045/d211845c-457e-4c3e-af1f-a0d654d3f365">	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.	1 year ago

Author

SHA1

Message

Date

JakobDev

4636f56e7b

Add Index to `action.user_id` (#27403 )

Another Column that needs a Index. Found at
https://codeberg.org/forgejo/discussions/issues/61#issuecomment-1258744.

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

1 year ago

Lunny Xiao

9c0a3532a4

Add a new column schedule_id for action_run to track (#26975 )

Fix #26971 

And the UI now will display it's scheduled but not triggered by a push.

<img width="954" alt="图片"
src="https://github.com/go-gitea/gitea/assets/81045/d211845c-457e-4c3e-af1f-a0d654d3f365">

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.

1 year ago

1 Commits (5687aca4fc9aef44e1fb5af655b2320d18583dbd)