2018-10-18 06:23:05 -05:00
|
|
|
// Copyright 2018 The Gitea Authors. All rights reserved.
|
2022-11-27 13:20:29 -05:00
|
|
|
// SPDX-License-Identifier: MIT
|
2016-12-30 11:44:54 -05:00
|
|
|
|
|
|
|
package notification
|
|
|
|
|
|
|
|
import (
|
2022-11-19 03:12:33 -05:00
|
|
|
"context"
|
|
|
|
|
2022-06-13 04:37:59 -05:00
|
|
|
issues_model "code.gitea.io/gitea/models/issues"
|
2022-03-30 03:42:47 -05:00
|
|
|
packages_model "code.gitea.io/gitea/models/packages"
|
2021-12-09 20:27:50 -05:00
|
|
|
repo_model "code.gitea.io/gitea/models/repo"
|
2021-11-24 04:49:20 -05:00
|
|
|
user_model "code.gitea.io/gitea/models/user"
|
2023-05-25 20:04:48 -05:00
|
|
|
"code.gitea.io/gitea/modules/git"
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-30 20:45:19 -05:00
|
|
|
"code.gitea.io/gitea/modules/log"
|
2019-11-03 15:59:09 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/action"
|
2018-10-18 06:23:05 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/base"
|
2019-01-17 09:23:22 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/indexer"
|
2019-01-13 09:42:55 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/mail"
|
2022-07-08 14:45:12 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/mirror"
|
2018-10-18 06:23:05 -05:00
|
|
|
"code.gitea.io/gitea/modules/notification/ui"
|
2020-01-10 04:34:21 -05:00
|
|
|
"code.gitea.io/gitea/modules/repository"
|
2019-10-25 09:46:37 -05:00
|
|
|
"code.gitea.io/gitea/modules/setting"
|
2016-12-30 11:44:54 -05:00
|
|
|
)
|
|
|
|
|
2022-01-20 12:46:10 -05:00
|
|
|
var notifiers []base.Notifier
|
2018-10-18 06:23:05 -05:00
|
|
|
|
|
|
|
// RegisterNotifier providers method to receive notify messages
|
|
|
|
func RegisterNotifier(notifier base.Notifier) {
|
|
|
|
go notifier.Run()
|
|
|
|
notifiers = append(notifiers, notifier)
|
|
|
|
}
|
|
|
|
|
2019-10-25 09:46:37 -05:00
|
|
|
// NewContext registers notification handlers
|
|
|
|
func NewContext() {
|
2018-10-18 06:23:05 -05:00
|
|
|
RegisterNotifier(ui.NewNotifier())
|
2019-10-25 09:46:37 -05:00
|
|
|
if setting.Service.EnableNotifyMail {
|
|
|
|
RegisterNotifier(mail.NewNotifier())
|
|
|
|
}
|
2019-01-17 09:23:22 -05:00
|
|
|
RegisterNotifier(indexer.NewNotifier())
|
2019-11-03 15:59:09 -05:00
|
|
|
RegisterNotifier(action.NewNotifier())
|
2022-07-08 14:45:12 -05:00
|
|
|
RegisterNotifier(mirror.NewNotifier())
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
|
2022-09-04 14:54:23 -05:00
|
|
|
// NotifyNewWikiPage notifies creating new wiki pages to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyNewWikiPage(ctx context.Context, doer *user_model.User, repo *repo_model.Repository, page, comment string) {
|
2022-09-04 14:54:23 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyNewWikiPage(ctx, doer, repo, page, comment)
|
2022-09-04 14:54:23 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyEditWikiPage notifies editing or renaming wiki pages to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyEditWikiPage(ctx context.Context, doer *user_model.User, repo *repo_model.Repository, page, comment string) {
|
2022-09-04 14:54:23 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyEditWikiPage(ctx, doer, repo, page, comment)
|
2022-09-04 14:54:23 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyDeleteWikiPage notifies deleting wiki pages to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyDeleteWikiPage(ctx context.Context, doer *user_model.User, repo *repo_model.Repository, page string) {
|
2022-09-04 14:54:23 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyDeleteWikiPage(ctx, doer, repo, page)
|
2022-09-04 14:54:23 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyCreateIssueComment notifies issue comment related message to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyCreateIssueComment(ctx context.Context, doer *user_model.User, repo *repo_model.Repository,
|
2022-06-13 04:37:59 -05:00
|
|
|
issue *issues_model.Issue, comment *issues_model.Comment, mentions []*user_model.User,
|
2022-02-23 15:16:07 -05:00
|
|
|
) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyCreateIssueComment(ctx, doer, repo, issue, comment, mentions)
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
2016-12-30 11:44:54 -05:00
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyNewIssue notifies new issue to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyNewIssue(ctx context.Context, issue *issues_model.Issue, mentions []*user_model.User) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyNewIssue(ctx, issue, mentions)
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
2016-12-30 11:44:54 -05:00
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyIssueChangeStatus notifies close or reopen issue to notifiers
|
2023-01-24 23:47:53 -05:00
|
|
|
func NotifyIssueChangeStatus(ctx context.Context, doer *user_model.User, commitID string, issue *issues_model.Issue, actionComment *issues_model.Comment, closeOrReopen bool) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-01-24 23:47:53 -05:00
|
|
|
notifier.NotifyIssueChangeStatus(ctx, doer, commitID, issue, actionComment, closeOrReopen)
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
2016-12-30 11:44:54 -05:00
|
|
|
|
2022-02-28 19:20:15 -05:00
|
|
|
// NotifyDeleteIssue notify when some issue deleted
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyDeleteIssue(ctx context.Context, doer *user_model.User, issue *issues_model.Issue) {
|
2022-02-28 19:20:15 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyDeleteIssue(ctx, doer, issue)
|
2022-02-28 19:20:15 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyMergePullRequest notifies merge pull request to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyMergePullRequest(ctx context.Context, doer *user_model.User, pr *issues_model.PullRequest) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyMergePullRequest(ctx, doer, pr)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-11-03 10:49:00 -05:00
|
|
|
// NotifyAutoMergePullRequest notifies merge pull request to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyAutoMergePullRequest(ctx context.Context, doer *user_model.User, pr *issues_model.PullRequest) {
|
2022-11-03 10:49:00 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyAutoMergePullRequest(ctx, doer, pr)
|
2022-11-03 10:49:00 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyNewPullRequest notifies new pull request to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyNewPullRequest(ctx context.Context, pr *issues_model.PullRequest, mentions []*user_model.User) {
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-30 20:45:19 -05:00
|
|
|
if err := pr.LoadIssue(ctx); err != nil {
|
|
|
|
log.Error("%v", err)
|
|
|
|
return
|
|
|
|
}
|
|
|
|
if err := pr.Issue.LoadPoster(ctx); err != nil {
|
|
|
|
return
|
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyNewPullRequest(ctx, pr, mentions)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-11-05 06:04:08 -05:00
|
|
|
// NotifyPullRequestSynchronized notifies Synchronized pull request
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPullRequestSynchronized(ctx context.Context, doer *user_model.User, pr *issues_model.PullRequest) {
|
2019-11-05 06:04:08 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullRequestSynchronized(ctx, doer, pr)
|
2019-11-05 06:04:08 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyPullRequestReview notifies new pull request review
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPullRequestReview(ctx context.Context, pr *issues_model.PullRequest, review *issues_model.Review, comment *issues_model.Comment, mentions []*user_model.User) {
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-30 20:45:19 -05:00
|
|
|
if err := review.LoadReviewer(ctx); err != nil {
|
|
|
|
log.Error("%v", err)
|
|
|
|
return
|
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullRequestReview(ctx, pr, review, comment, mentions)
|
2021-01-02 12:04:02 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyPullRequestCodeComment notifies new pull request code comment
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPullRequestCodeComment(ctx context.Context, pr *issues_model.PullRequest, comment *issues_model.Comment, mentions []*user_model.User) {
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-30 20:45:19 -05:00
|
|
|
if err := comment.LoadPoster(ctx); err != nil {
|
|
|
|
log.Error("LoadPoster: %v", err)
|
|
|
|
return
|
|
|
|
}
|
2021-01-02 12:04:02 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullRequestCodeComment(ctx, pr, comment, mentions)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-12-16 01:20:25 -05:00
|
|
|
// NotifyPullRequestChangeTargetBranch notifies when a pull request's target branch was changed
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPullRequestChangeTargetBranch(ctx context.Context, doer *user_model.User, pr *issues_model.PullRequest, oldBranch string) {
|
2019-12-16 01:20:25 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullRequestChangeTargetBranch(ctx, doer, pr, oldBranch)
|
2019-12-16 01:20:25 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-05-20 07:47:24 -05:00
|
|
|
// NotifyPullRequestPushCommits notifies when push commits to pull request's head branch
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPullRequestPushCommits(ctx context.Context, doer *user_model.User, pr *issues_model.PullRequest, comment *issues_model.Comment) {
|
2020-05-20 07:47:24 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullRequestPushCommits(ctx, doer, pr, comment)
|
2020-05-20 07:47:24 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-11-19 03:12:33 -05:00
|
|
|
// NotifyPullReviewDismiss notifies when a review was dismissed by repo admin
|
|
|
|
func NotifyPullReviewDismiss(ctx context.Context, doer *user_model.User, review *issues_model.Review, comment *issues_model.Comment) {
|
2021-02-11 12:32:25 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPullReviewDismiss(ctx, doer, review, comment)
|
2021-02-11 12:32:25 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyUpdateComment notifies update comment to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyUpdateComment(ctx context.Context, doer *user_model.User, c *issues_model.Comment, oldContent string) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyUpdateComment(ctx, doer, c, oldContent)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyDeleteComment notifies delete comment to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyDeleteComment(ctx context.Context, doer *user_model.User, c *issues_model.Comment) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyDeleteComment(ctx, doer, c)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyNewRelease notifies new release to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyNewRelease(ctx context.Context, rel *repo_model.Release) {
|
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-01-30 20:45:19 -05:00
|
|
|
if err := rel.LoadAttributes(ctx); err != nil {
|
|
|
|
log.Error("LoadPublisher: %v", err)
|
|
|
|
return
|
|
|
|
}
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyNewRelease(ctx, rel)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyUpdateRelease notifies update release to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyUpdateRelease(ctx context.Context, doer *user_model.User, rel *repo_model.Release) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyUpdateRelease(ctx, doer, rel)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyDeleteRelease notifies delete release to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyDeleteRelease(ctx context.Context, doer *user_model.User, rel *repo_model.Release) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyDeleteRelease(ctx, doer, rel)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyIssueChangeMilestone notifies change milestone to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeMilestone(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, oldMilestoneID int64) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeMilestone(ctx, doer, issue, oldMilestoneID)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyIssueChangeContent notifies change content to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeContent(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, oldContent string) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeContent(ctx, doer, issue, oldContent)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyIssueChangeAssignee notifies change content to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeAssignee(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, assignee *user_model.User, removed bool, comment *issues_model.Comment) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeAssignee(ctx, doer, issue, assignee, removed, comment)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-05-31 02:54:46 -05:00
|
|
|
// NotifyPullRequestReviewRequest notifies Request Review change
|
|
|
|
func NotifyPullRequestReviewRequest(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, reviewer *user_model.User, isRequest bool, comment *issues_model.Comment) {
|
2020-04-06 11:33:34 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-05-31 02:54:46 -05:00
|
|
|
notifier.NotifyPullRequestReviewRequest(ctx, doer, issue, reviewer, isRequest, comment)
|
2020-04-06 11:33:34 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyIssueClearLabels notifies clear labels to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueClearLabels(ctx context.Context, doer *user_model.User, issue *issues_model.Issue) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueClearLabels(ctx, doer, issue)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyIssueChangeTitle notifies change title to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeTitle(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, oldTitle string) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeTitle(ctx, doer, issue, oldTitle)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-09-08 11:29:51 -05:00
|
|
|
// NotifyIssueChangeRef notifies change reference to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeRef(ctx context.Context, doer *user_model.User, issue *issues_model.Issue, oldRef string) {
|
2020-09-08 11:29:51 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeRef(ctx, doer, issue, oldRef)
|
2020-09-08 11:29:51 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyIssueChangeLabels notifies change labels to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyIssueChangeLabels(ctx context.Context, doer *user_model.User, issue *issues_model.Issue,
|
2022-06-13 04:37:59 -05:00
|
|
|
addedLabels, removedLabels []*issues_model.Label,
|
2022-02-23 15:16:07 -05:00
|
|
|
) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyIssueChangeLabels(ctx, doer, issue, addedLabels, removedLabels)
|
2018-10-18 06:23:05 -05:00
|
|
|
}
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyCreateRepository notifies create repository to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyCreateRepository(ctx context.Context, doer, u *user_model.User, repo *repo_model.Repository) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyCreateRepository(ctx, doer, u, repo)
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-06-26 01:59:15 -05:00
|
|
|
// NotifyAdoptRepository notifies the adoption of a repository to notifiers
|
|
|
|
func NotifyAdoptRepository(ctx context.Context, doer, u *user_model.User, repo *repo_model.Repository) {
|
|
|
|
for _, notifier := range notifiers {
|
|
|
|
notifier.NotifyAdoptRepository(ctx, doer, u, repo)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 06:23:05 -05:00
|
|
|
// NotifyMigrateRepository notifies create repository to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyMigrateRepository(ctx context.Context, doer, u *user_model.User, repo *repo_model.Repository) {
|
2018-10-18 06:23:05 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyMigrateRepository(ctx, doer, u, repo)
|
2016-12-30 11:44:54 -05:00
|
|
|
}
|
|
|
|
}
|
2019-11-03 01:59:26 -05:00
|
|
|
|
2019-11-15 03:06:11 -05:00
|
|
|
// NotifyTransferRepository notifies create repository to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyTransferRepository(ctx context.Context, doer *user_model.User, repo *repo_model.Repository, newOwnerName string) {
|
2019-11-15 03:06:11 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyTransferRepository(ctx, doer, repo, newOwnerName)
|
2019-11-15 03:06:11 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyDeleteRepository notifies delete repository to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyDeleteRepository(ctx context.Context, doer *user_model.User, repo *repo_model.Repository) {
|
2019-11-15 03:06:11 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyDeleteRepository(ctx, doer, repo)
|
2019-11-15 03:06:11 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyForkRepository notifies fork repository to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyForkRepository(ctx context.Context, doer *user_model.User, oldRepo, repo *repo_model.Repository) {
|
2019-11-15 03:06:11 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyForkRepository(ctx, doer, oldRepo, repo)
|
2019-11-15 03:06:11 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyRenameRepository notifies repository renamed
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyRenameRepository(ctx context.Context, doer *user_model.User, repo *repo_model.Repository, oldName string) {
|
2019-11-15 03:06:11 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyRenameRepository(ctx, doer, repo, oldName)
|
2019-11-15 03:06:11 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-11-03 01:59:26 -05:00
|
|
|
// NotifyPushCommits notifies commits pushed to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPushCommits(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, opts *repository.PushUpdateOptions, commits *repository.PushCommits) {
|
2019-11-03 01:59:26 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPushCommits(ctx, pusher, repo, opts, commits)
|
2019-11-03 01:59:26 -05:00
|
|
|
}
|
|
|
|
}
|
2019-11-06 01:43:03 -05:00
|
|
|
|
|
|
|
// NotifyCreateRef notifies branch or tag creation to notifiers
|
2023-05-25 20:04:48 -05:00
|
|
|
func NotifyCreateRef(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, refFullName git.RefName, refID string) {
|
2019-11-06 01:43:03 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-05-25 20:04:48 -05:00
|
|
|
notifier.NotifyCreateRef(ctx, pusher, repo, refFullName, refID)
|
2019-11-06 01:43:03 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyDeleteRef notifies branch or tag deletion to notifiers
|
2023-05-25 20:04:48 -05:00
|
|
|
func NotifyDeleteRef(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, refFullName git.RefName) {
|
2019-11-06 01:43:03 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-05-25 20:04:48 -05:00
|
|
|
notifier.NotifyDeleteRef(ctx, pusher, repo, refFullName)
|
2019-11-06 01:43:03 -05:00
|
|
|
}
|
|
|
|
}
|
2019-11-24 00:16:59 -05:00
|
|
|
|
|
|
|
// NotifySyncPushCommits notifies commits pushed to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifySyncPushCommits(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, opts *repository.PushUpdateOptions, commits *repository.PushCommits) {
|
2019-11-24 00:16:59 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifySyncPushCommits(ctx, pusher, repo, opts, commits)
|
2019-11-24 00:16:59 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifySyncCreateRef notifies branch or tag creation to notifiers
|
2023-05-25 20:04:48 -05:00
|
|
|
func NotifySyncCreateRef(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, refFullName git.RefName, refID string) {
|
2019-11-24 00:16:59 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-05-25 20:04:48 -05:00
|
|
|
notifier.NotifySyncCreateRef(ctx, pusher, repo, refFullName, refID)
|
2019-11-24 00:16:59 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifySyncDeleteRef notifies branch or tag deletion to notifiers
|
2023-05-25 20:04:48 -05:00
|
|
|
func NotifySyncDeleteRef(ctx context.Context, pusher *user_model.User, repo *repo_model.Repository, refFullName git.RefName) {
|
2019-11-24 00:16:59 -05:00
|
|
|
for _, notifier := range notifiers {
|
2023-05-25 20:04:48 -05:00
|
|
|
notifier.NotifySyncDeleteRef(ctx, pusher, repo, refFullName)
|
2019-11-24 00:16:59 -05:00
|
|
|
}
|
|
|
|
}
|
2021-02-28 19:47:30 -05:00
|
|
|
|
|
|
|
// NotifyRepoPendingTransfer notifies creation of pending transfer to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyRepoPendingTransfer(ctx context.Context, doer, newOwner *user_model.User, repo *repo_model.Repository) {
|
2021-02-28 19:47:30 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyRepoPendingTransfer(ctx, doer, newOwner, repo)
|
2021-02-28 19:47:30 -05:00
|
|
|
}
|
|
|
|
}
|
2022-03-30 03:42:47 -05:00
|
|
|
|
|
|
|
// NotifyPackageCreate notifies creation of a package to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPackageCreate(ctx context.Context, doer *user_model.User, pd *packages_model.PackageDescriptor) {
|
2022-03-30 03:42:47 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPackageCreate(ctx, doer, pd)
|
2022-03-30 03:42:47 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// NotifyPackageDelete notifies deletion of a package to notifiers
|
2022-11-19 03:12:33 -05:00
|
|
|
func NotifyPackageDelete(ctx context.Context, doer *user_model.User, pd *packages_model.PackageDescriptor) {
|
2022-03-30 03:42:47 -05:00
|
|
|
for _, notifier := range notifiers {
|
2022-11-19 03:12:33 -05:00
|
|
|
notifier.NotifyPackageDelete(ctx, doer, pd)
|
2022-03-30 03:42:47 -05:00
|
|
|
}
|
|
|
|
}
|