If your developers live in GitHub, that’s where bug reports from your users should go. Not into an inbox someone has to copy from, and not into a separate dashboard nobody checks.
How it works: add the Saber Feedback button to your website or web app, connect it to a GitHub repository, and every feedback report becomes a new GitHub issue. Each issue includes the user’s message, their screenshot, the page they were on, and their browser and device details. Your users don’t need a GitHub account.
- Set up the GitHub integration in three steps
- What each GitHub issue includes
- Saber Feedback vs GitHub issue forms
- Ask for the feedback your team needs
- Frequently asked questions
Set up the GitHub integration in three steps
1. Add the feedback button to your site
Sign up for a 30-day free trial, create a feedback form, and paste the code snippet into your website. It takes a few minutes, and there are plugins and guides for WordPress, Shopify and other platforms. Our guide on how to add a feedback button to your website walks through it.
2. Connect your GitHub account
In the Saber Feedback app, open Third-party Integrations, click Setup New Integration and choose GitHub. Click Connect to GitHub and authorize Saber Feedback. There’s no token to copy: Saber Feedback connects to GitHub with OAuth, and works with private repositories as well as public ones.
Then choose the repository for new issues and set the issue title. You can include a summary of the user’s message in the title automatically. You can also add labels, such as user-feedback, so your team can tell these issues apart and filter them in one click.

3. Send a test report
Click Test Settings to send a sample report to GitHub and check the issue arrives as expected, then save. From then on, every feedback report from your site opens a new issue in that repository.
The GitHub integration help doc has every setting in detail.
What each GitHub issue includes
Saber Feedback collects the information a developer needs to reproduce a problem, so nobody has to go back to the user to ask which page, which browser, or what they saw. Each issue is written in Markdown and can include:
- The user’s message
- Any screenshot they attached
- Any category or rating they chose, if your form includes them
- The page URL
- The user’s browser, browser plugins, operating system and screen size
- The user’s email address, if they gave it or you passed it in from your app
- When the feedback was submitted
- A link back to the full report in your Saber Feedback account

Once the issue is in GitHub, you handle it like any other: assign it, add it to a project board or milestone, link it from a pull request, and close it when the fix ships.
Saber Feedback vs GitHub issue forms
GitHub’s issue forms and templates are great for bug reports from developers and open source contributors. But the person filling them in needs a GitHub account, has to leave your site to do it, and has to describe their browser and the page by hand. Most of your users won’t do that. Saber Feedback collects the report on the page where the problem happened.
| GitHub issue forms | Saber Feedback | |
|---|---|---|
| Who can report | People with a GitHub account and access to the repository | Anyone using your site |
| Where users give feedback | On GitHub | On any page of your site, from a feedback button |
| Screenshot of the page | Only if users take and upload one | Yes, taken from the feedback form |
| Page URL, browser and device details | Only if users type them | Added automatically |
| Works with private repositories | Only for people with access | Yes, users never see the repository |
| Price | Free | From $99/month, on plans with screenshots and integrations |
Ask for the feedback your team needs
Forms can be as simple or detailed as you like. Choose from 14 field types, including text boxes, dropdowns, checkboxes, and star and emoji ratings, and show follow-up questions based on earlier answers. You can use different forms on different parts of your site: a bug report form in your app, and a content feedback form on your marketing pages.

You can style the feedback button to match your site, or open the form from your own link or icon.
Frequently asked questions
Do my users need a GitHub account?
No. Users fill in the Saber Feedback form on your site, and Saber Feedback creates the issue using the GitHub account you connect. Your users never see GitHub.
Can I use it with a public repository?
You can, but issues in a public repository are public, so anything a user writes in the form, including their email address if you ask for it, can be read by anyone. We recommend a private repository for user feedback. If you turn on secure screenshots for a form, issues link to the screenshot in your Saber Feedback account instead of showing it, so only your team can see it.
Can I send feedback to more than one repository?
Yes. Each feedback form has its own integrations, so bug reports from your app can go to its repository, and feedback from your marketing site to another.
Can feedback go to other tools as well?
Yes. Saber Feedback also integrates with Jira, Linear, GitLab, Asana, Trello, Basecamp, Redmine and Slack, and can send feedback by email or webhook. See all integrations.
Where can I use the feedback button?
On almost any website or web app, including staging and test sites, client sites during a redesign, customer portals, WordPress and Shopify sites, and most learning management systems.
Try Saber Feedback with GitHub free for 30 days
Set up a feedback button that sends complete, actionable reports straight to GitHub. No credit card required.