Automating Bug Reports with Tally and Make

Description and use

<p>When building my first proper Android app, <a href="https://github.com/Benji377/Timety" rel="noopener noreferrer">Timety</a>, I ran into a common issue: I wanted to collect user feedback, but since my app is privacy-focused, I wanted to avoid forcing users to create an account just to report a bug.</p> <p>I found a great form-builder called <a href="https://tally.so" rel="noopener noreferrer">Tally</a> and created a feedback form. However, this introduced a new problem. Tally sends form submissions via email, but I manage my project board, bug reports, and feature requests on GitHub.</p> <p

Problem

<p>When building my first proper Android app, <a href="https://github.com/Benji377/Timety" rel="noopener noreferrer">Timety</a>, I ran into a common issue: I wanted to collect user feedback, but since my app is privacy-focused, I wanted to avoid forcing users to create an account just to report a bug.</p> <p>I found a great form-builder called <a href="https://tally.so" rel="noopener noreferrer">Tally</a> and created a feedback form. However, this introduced a new problem. Tally sends form submissions via email, but I manage my project board, bug reports, and feature requests on GitHub.</p> <p

Outcome

<p>When building my first proper Android app, <a href="https://github.com/Benji377/Timety" rel="noopener noreferrer">Timety</a>, I ran into a common issue: I wanted to collect user feedback, but since my app is privacy-focused, I wanted to avoid forcing users to create an account just to report a bug.</p> <p>I found a great form-builder called <a href="https://tally.so" rel="noopener noreferrer">Tally</a> and created a feedback form. However, this introduced a new problem. Tally sends form submissions via email, but I manage my project board, bug reports, and feature requests on GitHub.</p> <p

Evidence

Automating Bug Reports with Tally and Make

Source