Repository navigation
ci: post merges and releases to Slack - #48
Conversation
Same setup as the other plainlang repos: org bot token and channel, release results threaded under a start notice, failures broadcast, and a check-mark reaction on success. Merges use pull_request, not pull_request_target. The latter runs from main, which lags dev until a stable release.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Wires pyro into Slack the same way as the other plainlang repos. It uses the org
SLACK_BOT_TOKENsecret andSLACK_CHANNEL_IDvariable, and skips Slack when the variable is not shared with this repo.devpost one message. Release PRs are skipped becauserelease.ymlposts those. The trigger ispull_request, notpull_request_target, which runs frommainand so lagsdevuntil a stable release. Fork PRs get no secrets, so their merges post nothing; no fork PR has been merged here so far.notifyjob replies in its thread with the result. Failures are also broadcast to the channel, and success adds a ✅ reaction to the start notice. If there is no start notice, results post to the channel.