Skip to content

Add 08-slack-to-pr: scoped Slack mention to pull request - #9

Merged
hongyi-chen merged 2 commits into
mainfrom
hyc/example-08-slack-to-pr
Nov 10, 2026
Merged

hongyi-chen merged 2 commits into
mainfrom
hyc/example-08-slack-to-pr

Conversation

@hongyi-chen

@hongyi-chen hongyi-chen commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Why

Provide channel-scoped Slack intake without duplicate mention handlers.

What

  • Requests, clarifications, and PR links stay in the original thread; unmatched-event claims apply only to this route.
  • Setup preserves unrelated triggers, validates the definition, and opens a PR without applying it.

Verification

python3 scripts/check_conventions.py passed; python3 -m unittest discover -s scripts -p 'test_*.py' passed (12 tests).
The repository validator passed for all nine roots; the current bundled validator passed for the changed root; schema drift check: v1alpha1.
Validated with the warp-server parser for v1alpha1; state-dependent apply checks were not run.
No live apply, integration trial, or end-to-end factory run was performed. The Slack channel alias resolves at apply.

Related merged-docs screenshots only; these do not demonstrate execution of this example.

Computer-use screenshots (6)

Port 4321 monorepo factory page: "Check shared dependencies and involve their owners" verification instructions with pnpm code block
Port 4321 monorepo factory page: "Check shared dependencies and involve their owners" verification instructions with pnpm code block

Port 4322 Linear-to-pull-request page: "What comes back" section with claim-time state-handling wording
Port 4322 Linear-to-pull-request page: "What comes back" section with claim-time state-handling wording

Port 4323 Testing and tuning your factory: "Tune one setting" heading, table and numbered tuning steps
Port 4323 Testing and tuning your factory: "Tune one setting" heading, table and numbered tuning steps

Port 4323 Testing and tuning: "Test with a small change" trial instructions
Port 4323 Testing and tuning: "Test with a small change" trial instructions

Port 4321 testing page: single "Guide navigation" section with one intake list, followed by Related pages
Port 4321 testing page: single "Guide navigation" section with one intake list, followed by Related pages

Microservices guide "How a microservices factory is organized" section with four paragraphs and a summary table, rendered without overflow
Microservices guide "How a microservices factory is organized" section with four paragraphs and a summary table, rendered without overflow

Work-intake example (register T01, docs page G13). A slack/app_mention
automation filtered to one placeholder channel via the `channels` alias
starts a task; the foreman restates the deliverable in the originating
thread, asks one clarifying question and stops when the request is too
vague, dispatches a single implementation agent, and reports the PR link
back in the same thread. factory.yaml declares `integrations: [slack]`.

The README covers the trigger and filter keys verified against the live
v1alpha1 automation schema, what happens to mentions in other channels,
DMs, and thread replies (including `slack.autoRespondToThreadReplies`),
the account-linking prerequisite, a sample task with expected output,
validation, and a copyable setup prompt.

Validated with:
  python3 scripts/validate_factory_files.py examples/08-slack-to-pr/
  python3 scripts/check_conventions.py
  python3 -m unittest discover -s scripts -p 'test_*.py'
  for ex in examples/*/; do python3 scripts/validate_factory_files.py "$ex" || break; done
All pass; the channel alias is reported as a deferred resolution.

Co-Authored-By: Warp <agent@warp.dev>

@warp-agent-staging warp-agent-staging Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No material findings after reviewing the full diff, platform/source claims, parser validation and convention checks. CI is green; live integration setup and execution were not exercised.

Responding as Docs Factory (V2): Open session · View in factory

@warp-agent-staging

Copy link
Copy Markdown
Contributor

This PR was generated with Warp, requested by @hongyi-chen.

Comment @warp-staging-factory on this PR to send it follow-up work.

View run View conversation View on Slack

@warp-agent-staging
warp-agent-staging Bot marked this pull request as ready for review November 10, 2026 05:49

@warp-agent-staging warp-agent-staging Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the full diff against current docs and repository guidance. No findings. Conventions, helper tests, and v1alpha1 parser checks pass; CI is green. Live apply and integration trials were not run.

Responding as Docs Factory (V2): Open session · View in factory

@hongyi-chen
hongyi-chen merged commit a2545f4 into main Nov 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant