Show HN: Issue Embed – feedback fast straight to your GitHub Issues
1–6 of 6 posts
Re: Show HN: Issue Embed – feedback fast straight to your GitHub Issues
#2Hey HN creator of Issue Embed here, this is my lockdown project.
I wanted a tool to collect bugs on my websites but every other tool I could find would either want me to use their issue tracking platform or was too expensive. I just needed something simple for small websites, so I could receive issues straight into my GitHub Issues. I am able to use the issues in my current workflows. I scratched my own itch then a few friends asked to be able to use it too.
So here we are today, Issue Embed is on the GitHub Marketplace. I am launching a free plan. Any feedback is welcome.
Re: Show HN: Issue Embed – feedback fast straight to your GitHub Issues
#3Hey HN creator of Issue Embed here, this is my lockdown project. I wanted a tool to collect bugs on my websites but every other tool I could find would either want me to use their issue tracking platform or was too expensive. I just needed something simple for small websites, so I could receive issues straight into my GitHub Issues. I am able to use the issues in my current workflows. I scratched my own itch then a f…
Hi,
Congratulations with your launch.
Question: must an end user (web site visitor) do a (Github or other) login? Or can they simply leave a comment?
Re: Show HN: Issue Embed – feedback fast straight to your GitHub Issues
#4Hey HN creator of Issue Embed here, this is my lockdown project. I wanted a tool to collect bugs on my websites but every other tool I could find would either want me to use their issue tracking platform or was too expensive. I just needed something simple for small websites, so I could receive issues straight into my GitHub Issues. I am able to use the issues in my current workflows. I scratched my own itch then a f…
Hi, Congratulations with your launch. Question: must an end user (web site visitor) do a (Github or other) login? Or can they simply leave a comment?
Hey thank you very much. No login needed for submitting an issue. However follow up is handled differently:
Public repos: the reporter is given the link on successful submission, so to communicate further a GitHub account is required
Private repos: the reporter needs to supply an email (not shared with repo) which will be held by Issue Embed and handle communication from the issue to email (and visa-versa)
You can try a demo here: https://issueembed.dev/
Edit: formatting
Re: Show HN: Issue Embed – feedback fast straight to your GitHub Issues
#5Earlier quoted context omitted.
Hi, Congratulations with your launch. Question: must an end user (web site visitor) do a (Github or other) login? Or can they simply leave a comment?
Hey thank you very much. No login needed for submitting an issue. However follow up is handled differently: Public repos: the reporter is given the link on successful submission, so to communicate further a GitHub account is required Private repos: the reporter needs to supply an email (not shared with repo) which will be held by Issue Embed and handle communication from the issue to email (and visa-versa) You can tr…
I gave the reporting a try, and I like the flow in the demo (which is for a Public repo); easy to use.
For a private repo, I would probably also want people to be able to leave anonymous replies (to get 'as much feedback as possible'), but that's just my n=1 opinion.
Good luck.
Re: Show HN: Issue Embed – feedback fast straight to your GitHub Issues
#6Earlier quoted context omitted.
Hey thank you very much. No login needed for submitting an issue. However follow up is handled differently: Public repos: the reporter is given the link on successful submission, so to communicate further a GitHub account is required Private repos: the reporter needs to supply an email (not shared with repo) which will be held by Issue Embed and handle communication from the issue to email (and visa-versa) You can tr…
I gave the reporting a try, and I like the flow in the demo (which is for a Public repo); easy to use. For a private repo, I would probably also want people to be able to leave anonymous replies (to get 'as much feedback as possible'), but that's just my n=1 opinion. Good luck.
Thanks for the feedback, I have been thinking of whether making email optional or allowing the admin to not show it. Your feedback is a noted data point, thank you!