You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`.FallbackSubject`| string | Always | A default subject line. See Below. |
90
-
|`.Subject`| string | Only in body | The _subject_, once resolved. |
91
-
|`.Body`| string | Always | The message of the issue, pull request or comment, parsed from Markdown into HTML and sanitized. Do not confuse with the _mail body_|
92
-
|`.Link`| string | Always | The address of the originating issue, pull request or comment. |
93
-
|`.Issue`| models.Issue | Always | The issue (or pull request) originating the notification. To get data specific to a pull request (e.g. `HasMerged`), `.Issue.PullRequest` can be used, but care should be taken as this field will be `nil` if the issue is *not* a pull request. |
94
-
|`.Comment`| models.Comment | If applicable | If the notification is from a comment added to an issue or pull request, this will contain the information about the comment. |
95
-
|`.IsPull`| bool | Always |`true` if the mail notification is associated with a pull request (i.e. `.Issue.PullRequest` is not `nil`). |
96
-
|`.Repo`| string | Always | Name of the repository, including owner name (e.g. `mike/stuff`) |
97
-
|`.User`| models.User | Always | Owner of the repository from which the event originated. To get the user name (e.g. `mike`),`.User.Name` can be used. |
98
-
|`.Doer`| models.User | Always | User that executed the action triggering the notification event. To get the user name (e.g. `rhonda`), `.Doer.Name` can be used. |
99
-
|`.IsMention`| bool | Always |`true` if this notification was only generated because the user was mentioned in the comment, while not being subscribed to the source. It will be `false` if the recipient was subscribed to the issue or repository. |
100
-
|`.SubjectPrefix`| string | Always |`Re: ` if the notification is about other than issue or pull request creation; otherwise an empty string. |
101
-
|`.ActionType`| string | Always |`"issue"` or `"pull"`. Will correspond to the actual _action type_ independently of which template was selected. |
102
-
|`.ActionName`| string | Always | It will be one of the action types described above (`new`, `comment`, etc.), and will correspond to the actual _action name_ independently of which template was selected. |
|`.FallbackSubject`| string | Always | A default subject line. See Below. |
92
+
|`.Subject`| string | Only in body | The _subject_, once resolved. |
93
+
|`.Body`| string | Always | The message of the issue, pull request or comment, parsed from Markdown into HTML and sanitized. Do not confuse with the _mail body_. |
94
+
|`.Link`| string | Always | The address of the originating issue, pull request or comment. |
95
+
|`.Issue`| models.Issue | Always | The issue (or pull request) originating the notification. To get data specific to a pull request (e.g. `HasMerged`), `.Issue.PullRequest` can be used, but care should be taken as this field will be `nil` if the issue is *not* a pull request. |
96
+
|`.Comment`| models.Comment | If applicable | If the notification is from a comment added to an issue or pull request, this will contain the information about the comment. |
97
+
|`.IsPull`| bool | Always |`true` if the mail notification is associated with a pull request (i.e. `.Issue.PullRequest` is not `nil`). |
98
+
|`.Repo`| string | Always | Name of the repository, including owner name (e.g. `mike/stuff`) |
99
+
|`.User`| models.User | Always | Owner of the repository from which the event originated. To get the user name (e.g. `mike`),`.User.Name` can be used. |
100
+
|`.Doer`| models.User | Always | User that executed the action triggering the notification event. To get the user name (e.g. `rhonda`), `.Doer.Name` can be used. |
101
+
|`.IsMention`| bool | Always |`true` if this notification was only generated because the user was mentioned in the comment, while not being subscribed to the source. It will be `false` if the recipient was subscribed to the issue or repository. |
102
+
|`.SubjectPrefix`| string | Always |`Re: ` if the notification is about other than issue or pull request creation; otherwise an empty string. |
103
+
|`.ActionType`| string | Always |`"issue"` or `"pull"`. Will correspond to the actual _action type_ independently of which template was selected. |
104
+
|`.ActionName`| string | Always | It will be one of the action types described above (`new`, `comment`, etc.), and will correspond to the actual _action name_ independently of which template was selected. |
105
+
|`.ReviewComments`|[]models.Comment | Always | List of code comments in a review. The comment text will be in `.RenderedContent` and the referenced code will be in `.Patch`. |
103
106
104
107
All names are case sensitive.
105
108
@@ -254,13 +257,14 @@ This template produces something along these lines:
254
257
The template system contains several functions that can be used to further process and format
0 commit comments