Repository navigation
docs: deduplicate Slack setup, tunnel, and Linear stop sections - #82
Conversation
Moves the Linear example's maintainer-only dogfooding checklist into contributor docs (removed from the example README in #82). _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
@codex review |
|
@codex security review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8fcd7577cc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
@codex review |
|
@codex security review |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
@codex review |
|
@codex security review |
|
Rendered-docs evidence (GitHub preview of the branch at
Generated with |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
Make the Slack tutorial the one full walkthrough of Slack app setup. The four Slack example READMEs now link to its steps and keep a compact settings table plus their backend-specific instructions. The tutorial absorbs the unique details they carried (App Home troubleshooting, Funnel vs Serve, funnel reset, Slack doc links), and the reference absorbs the im:write note for DM fallback. The durable-state example READMEs promised subscribed-thread follow-ups but never asked for the channels:history scope or message.channels event, without which those follow-ups never reach the bot; the new settings table includes both. Also: drop the duplicated Run block and Tailscale section from the Linear example README, move its maintainer-only "Dogfooding Evidence" checklist out of user docs, point the Linear capability-gaps stop section at the how-to instead of repeating it, and remove a repeated adapter-tier row from the explanation's concept map. _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
_Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
Restores two details the deduplicated example READMEs carried. _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
a1e423b to
8483def
Compare
1 participant
Removes copied Slack setup text from the example READMEs and fixes a setup gap it was hiding. PR 3 of a docs cleanup; stacked on #80 (base
docs/fix-stale-facts). 9 files, +79 / −396.What changed
funnel resetnotes, and the Slack doc links.docs/reference.mdgains theim:writenote for ephemeral DM fallback.channels:historyscope or themessage.channelsevent, so those follow-ups never reach the bot. The new table includes both.CONTRIBUTING.mdin docs: rewrite README landing page and add CONTRIBUTING.md #81).Considered and kept: the per-adapter bullet lists in
docs/reference.mdoverlap the capability table but also carry details the table lacks (signature and replay checks, identity discovery, payload tolerance), so they stay.Validation
go test -run 'Documentation|README|Snippets' .passes.#step-5-expose-the-bot-to-slackand#use-the-full-activity-surfaceanchors.git diff --checkclean.Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high