2023-01-01 16:23:15 +01:00
|
|
|
// Copyright 2022 The Gitea Authors. All rights reserved.
|
|
|
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
|
|
|
|
|
|
package webhook
|
|
|
|
|
|
|
|
|
|
// HookEventType is the type of a hook event
|
|
|
|
|
type HookEventType string
|
|
|
|
|
|
|
|
|
|
// Types of hook events
|
Actions Failure, Succes, Recover Webhooks (#7508)
Implement Actions Success, Failure and Recover webhooks for Forgejo, Gitea, Gogs, Slack, Discord, DingTalk, Telegram, Microsoft Teams, Feishu / Lark Suite, Matrix, WeCom (Wechat Work), Packagist. Some of these webhooks have not been manually tested.
Implement settings for these new webhooks.
## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).
### Tests
- I added test coverage for Go changes...
- [x] in their respective `*_test.go` for unit tests.
- [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server.
- I added test coverage for JavaScript changes...
- [ ] in `web_src/js/*.test.js` if it can be unit tested.
- [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)).
### Documentation
- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.
### Release notes
- [ ] I do not want this change to show in the release notes.
- [x] I want the title to show in the release notes with a link to this pull request.
- [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
<!--start release-notes-assistant-->
## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Features
- [PR](https://codeberg.org/forgejo/forgejo/pulls/7508): <!--number 7508 --><!--line 0 --><!--description QWN0aW9ucyBGYWlsdXJlLCBTdWNjZXMsIFJlY292ZXIgV2ViaG9va3M=-->Actions Failure, Succes, Recover Webhooks<!--description-->
<!--end release-notes-assistant-->
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7508
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: christopher-besch <mail@chris-besch.com>
Co-committed-by: christopher-besch <mail@chris-besch.com>
2025-06-03 14:29:19 +02:00
|
|
|
// update TestCreateWebhook in models/webhook/webhook_test.go when adding or changing values here
|
2023-01-01 16:23:15 +01:00
|
|
|
const (
|
|
|
|
|
HookEventCreate HookEventType = "create"
|
|
|
|
|
HookEventDelete HookEventType = "delete"
|
|
|
|
|
HookEventFork HookEventType = "fork"
|
|
|
|
|
HookEventPush HookEventType = "push"
|
|
|
|
|
HookEventIssues HookEventType = "issues"
|
|
|
|
|
HookEventIssueAssign HookEventType = "issue_assign"
|
|
|
|
|
HookEventIssueLabel HookEventType = "issue_label"
|
|
|
|
|
HookEventIssueMilestone HookEventType = "issue_milestone"
|
|
|
|
|
HookEventIssueComment HookEventType = "issue_comment"
|
|
|
|
|
HookEventPullRequest HookEventType = "pull_request"
|
|
|
|
|
HookEventPullRequestAssign HookEventType = "pull_request_assign"
|
|
|
|
|
HookEventPullRequestLabel HookEventType = "pull_request_label"
|
|
|
|
|
HookEventPullRequestMilestone HookEventType = "pull_request_milestone"
|
|
|
|
|
HookEventPullRequestComment HookEventType = "pull_request_comment"
|
|
|
|
|
HookEventPullRequestReviewApproved HookEventType = "pull_request_review_approved"
|
|
|
|
|
HookEventPullRequestReviewRejected HookEventType = "pull_request_review_rejected"
|
|
|
|
|
HookEventPullRequestReviewComment HookEventType = "pull_request_review_comment"
|
|
|
|
|
HookEventPullRequestSync HookEventType = "pull_request_sync"
|
2023-05-25 10:06:27 +08:00
|
|
|
HookEventPullRequestReviewRequest HookEventType = "pull_request_review_request"
|
2023-01-01 16:23:15 +01:00
|
|
|
HookEventWiki HookEventType = "wiki"
|
|
|
|
|
HookEventRepository HookEventType = "repository"
|
|
|
|
|
HookEventRelease HookEventType = "release"
|
|
|
|
|
HookEventPackage HookEventType = "package"
|
2024-01-13 05:50:38 +08:00
|
|
|
HookEventSchedule HookEventType = "schedule"
|
2024-06-28 05:17:11 +00:00
|
|
|
HookEventWorkflowDispatch HookEventType = "workflow_dispatch"
|
Actions Failure, Succes, Recover Webhooks (#7508)
Implement Actions Success, Failure and Recover webhooks for Forgejo, Gitea, Gogs, Slack, Discord, DingTalk, Telegram, Microsoft Teams, Feishu / Lark Suite, Matrix, WeCom (Wechat Work), Packagist. Some of these webhooks have not been manually tested.
Implement settings for these new webhooks.
## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).
### Tests
- I added test coverage for Go changes...
- [x] in their respective `*_test.go` for unit tests.
- [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server.
- I added test coverage for JavaScript changes...
- [ ] in `web_src/js/*.test.js` if it can be unit tested.
- [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)).
### Documentation
- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.
### Release notes
- [ ] I do not want this change to show in the release notes.
- [x] I want the title to show in the release notes with a link to this pull request.
- [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
<!--start release-notes-assistant-->
## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Features
- [PR](https://codeberg.org/forgejo/forgejo/pulls/7508): <!--number 7508 --><!--line 0 --><!--description QWN0aW9ucyBGYWlsdXJlLCBTdWNjZXMsIFJlY292ZXIgV2ViaG9va3M=-->Actions Failure, Succes, Recover Webhooks<!--description-->
<!--end release-notes-assistant-->
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7508
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: christopher-besch <mail@chris-besch.com>
Co-committed-by: christopher-besch <mail@chris-besch.com>
2025-06-03 14:29:19 +02:00
|
|
|
HookEventActionRunFailure HookEventType = "action_run_failure"
|
|
|
|
|
HookEventActionRunRecover HookEventType = "action_run_recover"
|
|
|
|
|
HookEventActionRunSuccess HookEventType = "action_run_success"
|
2023-01-01 16:23:15 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
// Event returns the HookEventType as an event string
|
|
|
|
|
func (h HookEventType) Event() string {
|
|
|
|
|
switch h {
|
|
|
|
|
case HookEventCreate:
|
|
|
|
|
return "create"
|
|
|
|
|
case HookEventDelete:
|
|
|
|
|
return "delete"
|
|
|
|
|
case HookEventFork:
|
|
|
|
|
return "fork"
|
|
|
|
|
case HookEventPush:
|
|
|
|
|
return "push"
|
|
|
|
|
case HookEventIssues, HookEventIssueAssign, HookEventIssueLabel, HookEventIssueMilestone:
|
|
|
|
|
return "issues"
|
|
|
|
|
case HookEventPullRequest, HookEventPullRequestAssign, HookEventPullRequestLabel, HookEventPullRequestMilestone,
|
2023-05-25 10:06:27 +08:00
|
|
|
HookEventPullRequestSync, HookEventPullRequestReviewRequest:
|
2023-01-01 16:23:15 +01:00
|
|
|
return "pull_request"
|
|
|
|
|
case HookEventIssueComment, HookEventPullRequestComment:
|
|
|
|
|
return "issue_comment"
|
|
|
|
|
case HookEventPullRequestReviewApproved:
|
|
|
|
|
return "pull_request_approved"
|
|
|
|
|
case HookEventPullRequestReviewRejected:
|
|
|
|
|
return "pull_request_rejected"
|
|
|
|
|
case HookEventPullRequestReviewComment:
|
|
|
|
|
return "pull_request_comment"
|
|
|
|
|
case HookEventWiki:
|
|
|
|
|
return "wiki"
|
|
|
|
|
case HookEventRepository:
|
|
|
|
|
return "repository"
|
|
|
|
|
case HookEventRelease:
|
|
|
|
|
return "release"
|
Actions Failure, Succes, Recover Webhooks (#7508)
Implement Actions Success, Failure and Recover webhooks for Forgejo, Gitea, Gogs, Slack, Discord, DingTalk, Telegram, Microsoft Teams, Feishu / Lark Suite, Matrix, WeCom (Wechat Work), Packagist. Some of these webhooks have not been manually tested.
Implement settings for these new webhooks.
## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).
### Tests
- I added test coverage for Go changes...
- [x] in their respective `*_test.go` for unit tests.
- [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server.
- I added test coverage for JavaScript changes...
- [ ] in `web_src/js/*.test.js` if it can be unit tested.
- [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)).
### Documentation
- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.
### Release notes
- [ ] I do not want this change to show in the release notes.
- [x] I want the title to show in the release notes with a link to this pull request.
- [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
<!--start release-notes-assistant-->
## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Features
- [PR](https://codeberg.org/forgejo/forgejo/pulls/7508): <!--number 7508 --><!--line 0 --><!--description QWN0aW9ucyBGYWlsdXJlLCBTdWNjZXMsIFJlY292ZXIgV2ViaG9va3M=-->Actions Failure, Succes, Recover Webhooks<!--description-->
<!--end release-notes-assistant-->
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7508
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: christopher-besch <mail@chris-besch.com>
Co-committed-by: christopher-besch <mail@chris-besch.com>
2025-06-03 14:29:19 +02:00
|
|
|
case HookEventActionRunFailure:
|
|
|
|
|
return "action_run_failure"
|
|
|
|
|
case HookEventActionRunRecover:
|
|
|
|
|
return "action_run_recover"
|
|
|
|
|
case HookEventActionRunSuccess:
|
|
|
|
|
return "action_run_success"
|
2023-01-01 16:23:15 +01:00
|
|
|
}
|
|
|
|
|
return ""
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// HookType is the type of a webhook
|
|
|
|
|
type HookType = string
|
|
|
|
|
|
|
|
|
|
// Types of webhooks
|
|
|
|
|
const (
|
2024-03-13 16:49:48 +01:00
|
|
|
FORGEJO HookType = "forgejo"
|
|
|
|
|
GITEA HookType = "gitea"
|
|
|
|
|
GOGS HookType = "gogs"
|
|
|
|
|
SLACK HookType = "slack"
|
|
|
|
|
DISCORD HookType = "discord"
|
|
|
|
|
DINGTALK HookType = "dingtalk"
|
|
|
|
|
TELEGRAM HookType = "telegram"
|
|
|
|
|
MSTEAMS HookType = "msteams"
|
|
|
|
|
FEISHU HookType = "feishu"
|
|
|
|
|
MATRIX HookType = "matrix"
|
|
|
|
|
WECHATWORK HookType = "wechatwork"
|
|
|
|
|
PACKAGIST HookType = "packagist"
|
|
|
|
|
SOURCEHUT_BUILDS HookType = "sourcehut_builds" //nolint:revive
|
2023-01-01 16:23:15 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
// HookStatus is the status of a web hook
|
|
|
|
|
type HookStatus int
|
|
|
|
|
|
|
|
|
|
// Possible statuses of a web hook
|
|
|
|
|
const (
|
|
|
|
|
HookStatusNone HookStatus = iota
|
|
|
|
|
HookStatusSucceed
|
|
|
|
|
HookStatusFail
|
|
|
|
|
)
|