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), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Gitleaks] Build release binary in GitHub Actions

Requests that Gitleaks generate the executable on GitHub releases as part of the GitHub Actions release workflow, alongside the Docker container build process, to ensure broader compatibility.

Original Source

@@pcrockett | 1 pts | 9/18/2025

**Describe the solution you'd like** Generate the executable on GitHub releases as part of the release workflow in GitHub Actions, alongside the Docker container build process. I'd be happy to contribute a PR to do this, if that's a PR you'd accept. **Additional context** I have a very old 64-bit x86 CPU (manufactured in the Windows Vista-era) and gitleaks crashes on this machine when I try to run the executable from the latest release page. Here's the first part of the crash output: ``` SIGILL: illegal instruction PC=0x7f61be4f8a08 m=4 sigcode=2 instruction bytes: 0xf3 0x44 0xf 0xb8 0xc2 0x41 0x83 0xf8 0x1 0x41 0xf 0x97 0xc0 0x4d 0xf 0xb6 ``` However I extracted the executable from the official Docker image, and it runs just fine without any crash. I also happened to notice a lot of file paths like this in the crash output: * `/opt/homebrew/Cellar/go/1.24.1/libexec/src/runtime/proc.go` * `/Users/zrice/code/gitleaks-org/gitleaks/main.go` So it seems like the executable on the

Discussion

Loading comments...