Skip to content

docs(slack): starting with several repositories and the multi-select picker - #1051

Draft
ak684 wants to merge 1 commit into
mainfrom
alona/slack-multi-repo-start
Draft

ak684 wants to merge 1 commit into
mainfrom
alona/slack-multi-repo-start

Conversation

@ak684

@ak684 ak684 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor
  • I have read and reviewed the documentation changes to the best of my ability.
  • If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Summary of changes

The Slack pages describe starting a conversation with one repository. With OpenHands/enterprise#1086, a Slack message that names one or more repositories starts with all of them (the first is the main repository), and the picker, shown when the message names none, lets the user select several repositories and press Start or continue without one.

  • Cloud Slack page: replace the "Pro tip" with how to name repositories (owner/repo or a URL), the 10-repository limit, what the reply lists, and the multi-select picker. The old tip's "the openhands repo" form is not matched by the integration.
  • Enterprise Slack page: update the repository-selection note and the verification step.

Merge after OpenHands/enterprise#1086 ships.

@mintlify

mintlify Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
all-hands-ai 🟢 Ready View Preview Oct 29, 2026, 7:25 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@ak684

ak684 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

@OpenHands /codereview-roasted

Review exactly commit d3c89fe. If the PR head changes, report that and do not approve another commit. Review only: do not push code, merge, deploy, or change attribution. Check correctness, regression coverage, and whether the PR validation claims match the evidence. Keep code comments short. Post the substantive review and link it in your completion message. End the substantive review with these plain lines (no code fence), choosing one verdict:

REVIEWED_HEAD: d3c89fe
REVIEW_REQUEST: d59108ae8c754d3c937e0e02b3aa486c
VERDICT: APPROVED

Use VERDICT: CHANGES_REQUESTED instead when findings require changes. If unable to review, explain the blocker without an approval verdict.

@openhands-ai

openhands-ai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Uh oh! There was an unexpected error starting the job :(

This branch was successfully deployed

1 active deployment
staging — d3c89feb Deployed Oct 29, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant