[Improve] Clarify setup integration history - #2539
Open
roomote-roomote[bot] wants to merge 1 commit into
Open
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 11, 2026 18:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Asked about integrationsin conversation history.Why this change was made
The setup integration flow already follows source control and precedes starter-task suggestions. This follow-up makes its completed state use the intended conversational language and visual identity.
Impact
Users see
Asked about integrationsafter completing or skipping the optional integration step. The existing category order, recommendations, Connect actions, and first-class Keep going path are unchanged.Validation
Screenshots
The real setup component was rendered with representative integration options for layout validation; these screenshots do not prove backend discovery or OAuth behavior.