Flunes
Start free

How it works

A straight handoff from outside feedback to GitHub.

Flunes narrows the intake step so collaborators can report issues cleanly, GitHub can stay the execution layer, and nobody has to translate messages into tickets by hand.

Four steps, no triage inbox

From a shared link to a clean GitHub issue, and back.

  1. 01Step 1

    Connect a repo and share one link

    Sign in with GitHub, pick the repo, and share a focused intake link instead of GitHub access, Slack threads, or inbox forwarding.

    • Works with public and private repos
    • A separate link per collaborator keeps history clean
    Your repo intake link
    acme-inc/web-app
    flunes.com/s/acme-web

    Teammates with the link can report. They never see your code or your GitHub.

  2. 02Step 2

    Collaborators submit without accounts

    People report bugs and requests in a form built for non-technical contributors, with screenshots when the plan allows it. No account, no install.

    • Bug, feature request, or other
    • They set a priority; you can override it later
    What they fill in
    DW
    Dana Wu
    via the feedback link · no account
    1 screenshot attached
  3. 03Step 3

    Repo-aware AI structures the report

    Flunes reads your repo's README, topics, and file tree, then writes a structured GitHub issue with a 'Potential Areas to Investigate' section pointing at the most likely-relevant paths.

    • Repo-aware 'Potential Areas to Investigate'
    • Hit your AI limit? It still files a raw issue, nothing is dropped
    What lands in GitHub
    Checkout spinner never stops on mobile
    #128
    bugpriority: highcheckout
    Summary

    The checkout spinner on mobile Safari hangs indefinitely after the Pay CTA is tapped, blocking order completion.

    Observed Behavior

    After tapping Pay, the loading spinner appears and remains visible for over a minute without redirecting or showing an error.

    Expected Behavior

    Tapping Pay should redirect to the order confirmation page or display a recoverable error state.

    Potential Areas to InvestigateNew
    • apps/checkout/mobile/payment-flow.ts
    • apps/checkout/components/PayButton.tsx
    • src/lib/stripe/confirm-handler.ts
  4. 04Step 4

    Two-way replies without GitHub access

    People follow progress and reply to dev follow-ups in-app or by email, without joining the engineering workflow. Replies sync back to the GitHub thread automatically.

    • No account for them, no new tab for you
    • The original submission stays linked for context
    The reply thread
    SR
    Sam Riverafrom GitHub

    Thanks, this is fixed in the next release. Were you on iOS or Android when it happened?

    DW
    Dana Wuby email reply

    iOS, latest Safari. Just retried and it works now.

    Both replies sync to the GitHub issue thread. No GitHub seat needed.
Two sides, one loop

Cleaner intake for them, less translation for you.

For the people reporting

Report and follow up, no GitHub needed

  • One link to report a bug or idea, no account or install.
  • Follow status without chasing developers or asking for GitHub access.
  • Reply to dev follow-ups in-app or straight from the email notification.
For the team that ships

GitHub still owns execution

  • Triage, assign, and close where you already ship, GitHub stays the execution layer.
  • Every issue links back to the exact Flunes submission when you need the context.
  • Bulk-resolve from the dashboard to auto-close the linked GitHub issues in the background.

Flunes improves what enters GitHub. It does not replace it.

If this handoff is your bottleneck, start free.

Run it on one real repo first. Upgrade only when feedback volume makes the free tier too small.

Start free

No credit card. Connect one repo and share a link in minutes.