RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[KServe] Enhance release orchestrator agent for flexible working directory

Request to enhance the release-orchestrator.agent.md to support a flexible working directory. Currently, it assumes release work happens in the same repository, leading to tight coupling and limitations in testing agent improvements.

Original Source

@@Jooho | 0 pts | 15d ago

## Problem Current `release-orchestrator.agent.md` assumes release work happens in the same repository where the agent file exists. This creates tight coupling between agent development and release execution. **Current workflow limitations**: - Agent development and release work must share same kserve repo - All paths are relative (`./hack/release/`, `kserve-deps.env`) - Cannot safely test agent improvements during active releases ## Goal Enable separated workflows: - **Agent development**: One kserve repo for improving `.agent.md` - **Release execution**: Different kserve repo for actual release work - **Hot reload**: Agent changes apply on Copilot restart with checkpoint resume ## Required Changes ### 1. Working Directory Setup Add Phase 0 to detect/configure release repository: ```bash if [[ ! -f "kserve-deps.env" ]]; then read -p "Enter KServe repository path: " KSERVE_REPO_PATH cd "$KSERVE_REPO_PATH" fi ``` ### 2. Path Resolution Convert relative paths to work from co

Discussion

Loading comments...