forked from sopel-irc/sopel-github
-
Notifications
You must be signed in to change notification settings - Fork 0
/
NEWS
127 lines (91 loc) · 3.61 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
Changes in 0.2.4
================
Fixed:
* Comments with trailing whitespace incorrectly had `[…]` appended even if the
body contained only one line of (non-quoted) text (#50)
Changes in 0.2.3
================
Changed:
* Milestone name is now included in `demilestoned` webhook events (#46)
* GitHub originally didn't include this information in the webhook payload,
but started sending it in approximately late-summer 2019
Fixed:
* Comments that were not truncated would still have `[…]` appended if the
comment body included quoted text (#47)
Changes in 0.2.2
================
Changed:
* Comment bodies will be shortened to approx. 250 characters, to try and stay
within the length limit of one IRC line (#45)
Fixed:
* Repo URLs can be detected even with leading text on the line (#44)
Changes in 0.2.1
================
Fixed:
* Comments containing blank lines would cause errors (#43)
Changes in 0.2.0
================
Added:
* Handling for several new event types:
* Pull request reviews (#20)
* Pull request assignments (#23)
* Pull request labels (#23)
* Pull request milestones (#35)
* Issue & pull request title edits (#36)
* Releases (#21)
* Handling of draft pull requests (#34)
* Handling for draft pull requests marked ready for review (#34)
* Converting `:emoji:` to Unicode emoji in most text output (#17)
* Requires optional dependency: https://pypi.org/project/emoji/
Changed:
* `secret` setting is now called `client_secret` (#42)
* The plugin will automatically migrate configs to use the new name, but
manual editing is encouraged in advanced setups (e.g. if the user Sopel
runs as cannot write to the config file)
* Quoted text is ignored when generating comment output (#41)
* Unicode ellipsis now used instead of three periods (#31)
* Oxford comma now used in generated lists (#40)
* Webhook payload processing is handed off to a separate thread (#22)
* Bottle can handle only one request at a time; doing this should minimize
the potential for failed deliveries, as GitHub's webhook delivery service
times out very quickly
Fixed:
* GitHub URL regexes should match all possible usernames & repo names (#38)
* Of particular note: dots (`.`) are now recognized in repository links,
such as Sopel's website repo: https://github.com/sopel-irc/sopel.chat
Changes in 0.1.7
================
Fixed:
* Error with empty issue/PR description or commit message (#39)
Changes in 0.1.6
================
Changed:
* Webhook now says "merged" instead of "closed" for merged PRs (#18)
* Re-opened issues/PRs will also trigger the webhook now (#27)
Fixed:
* Webhook ignores issue, PR, and review comments that were edited (#16, #24)
* Commit summary correctly says "1 file" instead of "1 files" (#37)
* Some webhook output grammar fixed (#15)
* Handle comments submitted via email correctly WRT line-endings (#30)
* Replace uses of long-deprecated `SopelMemory` method (#33)
Changes in 0.1.5
================
Fixed:
* Refactoring unintentionally broke registering new repo webhooks (#14)
Meta:
* PyPI package description should be rendered to HTML now (fixed content-type)
Changes in 0.1.4
================
Changed:
* "GitHub" is now properly capitalized everywhere in text output (#9)
* Usage output uses `help_prefix` from config instead of hardcoded `.` (#12)
Fixed:
* git.io shortening was cutting off GET parameters of input links. (#11)
Changes in 0.1.3
================
Meta:
* Moved to Sopel organization on GitHub; new maintainer
Changed:
* Uses requests instead of deprecated sopel.web functions (Sopel itself
requires requests, so we don't have to.)
* Fetched git.io links use HTTPS now