Repository navigation
Superseded by merged PR #40 — Toolify software funnel (do not merge separately) - #38
Closed
appdevelopsk wants to merge 37 commits into
Closed
appdevelopsk wants to merge 37 commits into
appdevelopsk wants to merge 37 commits into
Conversation
appdevelopsk
changed the title
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.
Superseded by merged integration PR #40. The old #38 branch is 166 commits behind main and must not be merged separately: current main already contains the contextual
ToolSoftwareRecommendationsUI, catalog-gated software mappings, software click/process/download tracking, and the live-growth/HTML smoke scripts. These were verified by fetching six corresponding source files from main on 2026-11-07.Closing this obsolete PR prevents an older branch from overwriting newer combined implementation. This is a source-presence check, not an assertion of a successful production deployment or revenue increase.
Any post-merge embed HTML safety fixes are tracked in draft PR #41, not #38. No GitHub Actions execution, merge or deployment is performed as part of closing #38.