Why Post2Git Exists
Post2Git was born from a simple problem: important feedback rarely arrives when you’re calmly sitting in front of GitHub/GitLab. In real life, information comes up over coffee, on calls, on weekends, on the go — and that’s exactly when you lose details, context… and sometimes the idea itself.
Post2Git is a tool that turns WhatsApp messages (text or voice) into GitHub and GitLab issues, automatically.
Page linked from the LinkedIn post “The origin story of Post2Git”.
Post2Git helps with these needs
If you want a simple way to capture feedback when you’re not in front of your computer, Post2Git can help — especially to:
- Create a GitHub issue from WhatsApp
- Create a GitLab ticket from a message (text or voice)
- Turn informal conversations into traceable tasks
- Avoid forgetting feedback received in meetings, calls, or weekends
- Capture a product idea in the moment and formalize it automatically
The gap between informal feedback and GitHub/GitLab issues
Before Post2Git, my process often looked like this:
- I kept the info in my head thinking “don’t forget”
- If I had time: a phone note, an email, or a message to myself
- Later (often much later), I rewrote and clarified it
- Only then, I created a GitHub/GitLab issue so it became traceable
In real life, this delay creates losses: forgetting, missing details, unclear priorities, an outdated backlog. And once you multiply that by the number of people involved… it becomes systemic.
Before
- Phone note / email to yourself
- Rewrite later (often too late)
- Lost details & fuzzy priorities
- Issue created… or never
With Post2Git
- WhatsApp message (text or voice)
- Structured GitHub/GitLab issue in 30–60s
- Context captured in the moment
- Immediate traceability
When software traceability is mandatory (teams, compliance)
This is not just about convenience: in many teams, traceability and rigor are essential.
The real challenge: capture information when it appears, then turn it into an actionable, traceable issue without heroic effort (or any effort at all).
The solution: capture now, formalize automatically
Post2Git turns your WhatsApp messages (text or voice) into GitHub or GitLab issues in 30–60 seconds. You capture the idea as it happens — and your repo receives a clear, structured, traceable task.
Example (WhatsApp message)
Result (issues)
- Issue: Fix Android sync bug (steps + context)
- Issue: Add a regression test
- Issue: Adjust button wording (UI)
That’s exactly what Post2Git does: you send the info in the moment, and you get clean, traceable issues in your repo.
Tip: when you’re on the go, send a voice note → Post2Git transcribes it and creates the issues.
FAQ — Why Post2Git?
Because the problem happens outside tools: the goal is to capture fast, at the right time, with no friction and no context switching.
No. Post2Git complements your repo: it turns informal inputs into traceable issues, it doesn’t replace your workflow.
On GitHub (OAuth), Post2Git may require the repo scope (full access to private repositories) to create issues in private projects. On GitLab, creating issues via the API often requires the api scope. We apply least privilege by recommending access only to the necessary projects and revoking access when it’s no longer needed.
If you want to stay in control, Post2Git can offer a validation step (summary + issues) before creation. If this mode isn’t enabled on your account, contact us.
Post2Git uses your message content only to generate issues (title, description, context). Details about processing and retention are described in the Privacy page.
Typically 30 to 60 seconds. You send a message (text or voice) and Post2Git replies with a summary and the created issues.
Yes. The more people involved, the more information gets lost in the gap between discussions and the repo. Post2Git reduces those losses.