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
- Removes the slack commands that dispatch tweets etc via slack
- Removes the listener that tweets out GitHub releases
- Removes the twitter webhook that reacts to tweets and posts them to a slack channel
- Removes all configuration relating to twitter
- Removes dependencies on laminas-twitter
- Removes the twitter link in the layout
- Removes twitter related documentation from the README
Signed-off-by: George Steel <george@net-glue.co.uk>
-`/reply-to-tweet {url} {message}` allows replying to a tweet as specified by
50
-
`{url}` via the [@getlaminas](https://twitter.com/getlaminas) twitter account.
51
-
52
-
- A webhook for incoming tweets. This webhook works in conjunction with a recipe
53
-
on IFTTT that monitors tweets on the getlaminas account, and then passes them
54
-
to our webhook. The webhook queues a job that sends the tweet details to a
55
-
configured Slack channel.
56
43
57
44
### Requirements
58
45
@@ -77,9 +64,6 @@ The Laminas Bot acts as:
77
64
- /regenerate-tsc-list
78
65
- /register-repo {repo}
79
66
- /build-docs {repo}
80
-
- /tweet [media:url] {message}
81
-
- /retweet {url}
82
-
- /reply-to-tweet {url} {message}
83
67
- Setup an incoming webhook
84
68
- Add location to SLACK_WEBHOOK_LOGGING
85
69
- Invite the bot to #technical-steering-committee and #laminasbot-errors
@@ -93,15 +77,6 @@ The Laminas Bot acts as:
93
77
- From Discourse
94
78
- We need a signing secret; this can be arbitrary, but once used, must be used
95
79
when registering ALL webhooks. Add to DISCOURSE_SECRET
96
-
97
-
- From Twitter
98
-
- We need the access token and secret, and the consumer key and secret, as:
99
-
- TWITTER_ACCESS_TOKEN
100
-
- TWITTER_ACCESS_SECRET
101
-
- TWITTER_CONSUMER_KEY
102
-
- TWITTER_CONSUMER_SECRET
103
-
- We need the shared token between IFTTT and the website for accepting tweets
104
-
as TWEET_VERIFICATION_TOKEN.
105
80
106
81
- From Mastodon
107
82
- We need access credentials from a created app as
@@ -116,7 +91,7 @@ The Laminas Bot acts as:
116
91
117
92
#### Handlers
118
93
119
-
There are four primary endpoints:
94
+
There are three primary endpoints:
120
95
121
96
-`/api/discourse/[:channel]/:event` is an incoming webhook from Discourse. The
122
97
`:channel` is the name of the Slack channel to notify, and the `:event`
@@ -136,12 +111,6 @@ There are four primary endpoints:
136
111
implementation and dispatch. Individual implementations marshal appropriate
137
112
events to dispatch via the event dispatcher.
138
113
139
-
-`/api/twitter/[:token]` is an incoming webhook from IFTTT. The `:token` is the
140
-
shared token between the IFTTT and the webhook; if not identical, requests are
141
-
rejected. They payload must contain the elements text, url, and timestamp, and
142
-
is used to dispatch an `App\Twitter\Tweet` event before returning a 202
143
-
response.
144
-
145
114
#### Events
146
115
147
116
The repository provides the following event types, with the listed handlers.
@@ -153,14 +122,10 @@ Event Type | Handler(s) | Action taken
153
122
`App\GitHub\Event\GitHubIssue` | `App\GitHub\Listener\GitHubIssueListener` | Send a notification to Slack about issue creation or closure.
154
123
`App\GitHub\Event\GitHubIssueComment` | `App\GitHub\Listener\GitHubIssueCommentListener` | Send a notification to Slack about comment creation on an issue or pull request.
155
124
`App\GitHub\Event\GitHubPullRequest` | `App\GitHub\Listener\GitHubPullRequestListener` | Send a notification to Slack about pull request creation or closure.
156
-
`App\GitHub\Event\GitHubRelease` | `App\GitHub\Listener\GitHubRelease\SlackListener`, `App\GitHub\Listener\GitHubReleaseTweetListener`, `App\GitHub\Listener\GitHubReleaseWebsiteUpdateListener` | Send a notification to Slack about release creation; tweet the release details; and notify the website of the release so it can update the release RSS feed.
125
+
`App\GitHub\Event\GitHubRelease` | `App\GitHub\Listener\GitHubRelease\SlackListener`, `App\GitHub\Listener\GitHubReleaseWebsiteUpdateListener` | Send a notification to Slack about release creation and notify the website of the release so it can update the release RSS feed.
157
126
`App\GitHub\Event\GitHubStatus` | `App\GitHub\Listener\GitHubStatusListener` | Send a notification to Slack about a build failure, error, or success.
158
127
`App\GitHub\Event\RegisterWebhook` | `App\GitHub\Listener\RegisterWebhookListener` | Use the GitHub API to register the Laminas-BOT webhook with the given repository.
159
128
`App\Slack\Event\RegenerateAuthorizedUserList` | `App\Slack\Listener\RegenerateAuthorizedUserListListener` | Use the Slack Web API to rebuild the list of authorized slash command users from the current #technical-steering-committee list.
160
-
`App\Slack\Event\Retweet` | `App\Slack\Listener\RetweetListener` | Use the Twitter API to retweet a given tweet.
161
-
`App\Slack\Event\Tweet` | `App\Slack\Listener\TweetListener` | Use the Twitter API to send a tweet.
162
-
`App\Slack\Event\TwitterReply` | `App\Slack\Listener\TwitterReplyListener` | Use the Twitter API to send a message in reply to another tweet.
163
-
`App\Twitter\Tweet` | `App\Twitter\TweetListener` | Send a Slack message to a configured channel with details on a single tweet.
164
129
165
130
All listeners are decorated using the `DeferredServiceListenerDelegator` class
166
131
from the phly/phly-swoole-taskworker package. This means that they will be
@@ -236,6 +201,3 @@ All of these objects support:
236
201
technical steering committee members. If not, an error message is returned to
237
202
the user immediately. The list is generated on application initialization, and
238
203
again on receipt of a /regenerate-tsc-list command.
239
-
240
-
- A shared secret is configured between IFTTT and the Twitter webhook, and we
0 commit comments