mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-07-13 04:58:46 +00:00
- add the NewReaction and DeleteReaction interface and loop to the notify service - use services/issue instead of models/issues in REST and web API to create and delete reactions - Issues and Comment reactions created via services/issue notify via NewReaction - Issues and Comment reactions deleted via services/issue notify via DeleteReaction ### Tests for Go changes - I added test coverage for Go changes... - [x] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### 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 - [ ] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [x] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13017 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org> |
||
|---|---|---|
| .. | ||
| assignee.go | ||
| assignee_test.go | ||
| comments.go | ||
| comments_test.go | ||
| commit.go | ||
| commit_test.go | ||
| content.go | ||
| issue.go | ||
| issue_test.go | ||
| label.go | ||
| label_test.go | ||
| main_test.go | ||
| milestone.go | ||
| milestone_test.go | ||
| pull.go | ||
| reaction.go | ||
| reaction_test.go | ||
| status.go | ||
| template.go | ||